Fatal: (c:\torque\sdk\engine\platformwin32\winfileio.cc...
by Corin · in Torque Game Engine · 12/08/2005 (3:22 am) · 7 replies
About the author
#2
12/08/2005 (9:55 am)
Quickest way to track this down is to set a breakpoint on the Con::Warn or Con::printf lines in filestream.cc, then when it breaks you can find out what file it is warning you about.
#3
12/08/2005 (10:32 am)
Is your filesystem valid & reliable?
#4
I realize that those files just have the error kicker, so I'm not sure where the true problem is.
I found that when I try and place a new triggger of ANY type (including ones that previously worked) I catch the error. Here is the dialouge box:
http://project.ubergaming.net/pic/error.jpg
12/08/2005 (2:29 pm)
@Ben I think the problem may stem from the fact we are using Perforce for version control. It sets all files that are not checked out to "read-only". However, I do have filestream.cc and filestream.h checked out.I realize that those files just have the error kicker, so I'm not sure where the true problem is.
I found that when I try and place a new triggger of ANY type (including ones that previously worked) I catch the error. Here is the dialouge box:
http://project.ubergaming.net/pic/error.jpg
#5
12/09/2005 (12:27 pm)
I desperately need to solve this issue. Can anyone help? This has completely stopped me from placing any new triggers. I'm not sure when it started, but this definitely didn't use to happen.
#6
bzztbomb
[url="http://knowhere.net/"]Knowhere Studios[/url]
12/09/2005 (3:07 pm)
Try the debugger thing I mentioned above. Also you might want to try making all of your files read/write. bzztbomb
[url="http://knowhere.net/"]Knowhere Studios[/url]
#7
12/09/2005 (7:05 pm)
I just made the entire repository writtable and that seemed to work. Problem solved, thanks for helping out guys.
Torque 3D Owner Thomas Shaw