|
Author
|
Topic: Win2000 & SDOE - Almost, but not quite... (help!)
|
JG3_Jetlag
Pilot
|
posted 11-19- 09:10 AM
   
I have a problem when running SDOE in Windows 2000. The game runs fine for a while, good framerates etc., then when I press a fire button the game pauses for couple of seconds as it loads a texture (tracer or gun flash) then resumes as normal. The game also pauses the first time a "gun hit" texture is drawn and a "dust" or "water" splash. After a short while longer the game will freeze totally. Checking the error log I get this message printed over and over:-
code:
Message: TexCache::g3loadtexture Near infinite loop waiting for texture!!
I have Win2000 with SP1, DirectX 8, running on an AMD Thunderbird 1GHz, KT7-RAID, 384Mb RAM, GeForce2 GTS 32Mb RAM and Detonator3 6.47 (also same with 6.31). SDOE runs fine with the the same under WinMe. I have tried deleting the cache files. Is the game locking-up because the error log gets too long (this message gets printed 100's of times)? Any help/ideas appreciated. ------------------
9./JG3_Jetlag
 IP: Logged |
Pye
Pilot
|
posted 11-19- 11:09 AM
I have proved that the Detonator Drivers Have got some problems. 3.68 Are the last known drivers that work will all my software ((Geforce256 original here). I have now gone back to these drivers. And don't notice any FPS loss, Thats mainly due to the fact that My PC133 memory is is now being used! :-) perhaps. Windows version was 3.78 not unified! (966kb) not unified. I still have a copy of these if you want it! Detonator 2 (5.22) stop Rogue spear main screen appearing properly and the game stutters really bad, This happens on all later version of Geforce drivers Detonator 3 (6.18 & 6.31) Stops Shogun -Total War from loading!! So you see Thats it's not a good upgrade, after all, I've found out!
Anyone Found any other problems with Detonator drivers fir the Geforce , please comment. IP: Logged |
JG3_Jetlag
Pilot
|
posted 11-19- 11:46 AM
I don't think it is a Detonator problem.I should add, I disabled the indexing of files in Win2000, but that didn't make a difference. On a side note: The difference in framrates when using a digital stick rather than an analogue one in Win2000 is huge. 70fps vs 50fps for an in-cockpit view! ------------------
9./JG3_Jetlag
IP: Logged |
Pachy
Pilot
|
posted 12-20- 02:20 AM
*Bump*Jetlag, did you fix that problem eventually? I have exactly the same, only worse (more than 5 seconds of pausing before texture loads) under Win XP with a GF3Ti500. IP: Logged |
ArgonV
JAG
|
posted 12-20- 02:30 AM
Same problem here with Win XP... Any ideas? I havent had it froze up on me yet tho!P.S. Thank God I installed WinXP on a totally different hard drive and kept my Win98 SE install!!!  IP: Logged |
Maury Markowitz
Pilot
|
posted 12-20- 09:00 AM
Just to be contrarian, I'm under 2K with a GeForce and everything is pretty much perfect. At least once I turned on compatibility mode.Maury IP: Logged |
Pachy
Pilot
|
posted 12-20- 09:49 AM
At the risk of sounding very stupid, what's "compatibility mode"?IP: Logged |
Lothar
Pilot
|
posted 12-20- 10:48 AM
I have crashes under Win2k with a Geforce2mx also. Additionally, the labels on the buttons in the Options menu don't show on many items. I also have the infinate loop message in my log file.
I've tried the various compatibility modes, but I haven't installed old nvidia drivers.IP: Logged |
Maury Markowitz
Pilot
|
posted 12-20- 12:58 PM
quote:
Originally posted by Pachy:
At the risk of sounding very stupid, what's "compatibility mode"?
If you have SP2 installed you make a shortcut to the app and then get properties on it. You'll see a new tab called "compatibility" (or something) and if you select Win98 it runs better. Maury IP: Logged |
Pachy
Pilot
|
posted 12-20- 02:22 PM
"Compatibility mode" did the trick! Thanks a ton Maury!ALL 2000/XP USERS TRY THIS IF YOU EXPERIENCE PAUSES!!! IP: Logged |
ArgonV
JAG
|
posted 12-20- 03:22 PM
Just tried this last night before I read this post, it DOES work!!!!!!! IP: Logged |
Maury Markowitz
Pilot
|
posted 12-21- 08:24 AM
quote:
Originally posted by Pachy:
"Compatibility mode" did the trick! Thanks a ton Maury!
Hey cool. But I'd still like to know exactly what this does so we can just put it in the patch. However no one seems to know exactly what compatibility mode is, and posts on the MS newsgroups go unanswered. Maury IP: Logged |
JG3_Jetlag
Pilot
|
posted 12-31- 10:04 AM
quote:
Originally posted by Pachy:
*Bump*Jetlag, did you fix that problem eventually? I have exactly the same, only worse (more than 5 seconds of pausing before texture loads) under Win XP with a GF3Ti500.
Once I worked out I need to right-click on the shortcut to the exe to find the compatability options and not the exe itself it worked fine. Thanks for asking.  IP: Logged |
Major Hippie
Pilot
|
posted 12-31- 11:15 AM
I've been having XP lag in SDOE as well, switched on the compatabilty mode, pausing is gone in Direct3D, but I get a crash & an error report message when I try to run compatablity on SDOE in OpenGL. any clues on whay compat mode won't work with OpenGL..hip63 
------------------
...remember always fly HIGH!!!
http://groovygalaxy.50megs.com/psychedelicsquadron.html IP: Logged |
Maury Markowitz
Pilot
|
posted 01-01- 05:09 PM
I've never been able to find out what that switch does. I'm guessing, but I think it might tell the 2k kernel to change the event timing loops for the app. The app might be relying on how the 95 event loop timing works, and uses that to do screen or texture updates. If the loop doesn't run as much (or at the same times) under 2k it might time out waiting for a chance.Anyone know any Win gurus they can ask? Maury IP: Logged |
ArgonV
JAG
|
posted 01-01- 08:54 PM
Hippie, Im running in compatability mode and OpenGL with WinXP. Every thing is fine here!  IP: Logged |
FSIC Messageboard
UBBFriend: Email This Page to Someone! 
