Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: nall on May 30, 2004, 10:05:16 am
-
well this game never exactly liked my graphics card for some reason.. but this cmd seems to be compeletly random. Ive had it happen five times and it just keeps happening. Right now im on mission three.. and i can only get half way before it just crashes. This has happened on the previous missions.. but there didint last long enough to crash all the time.
crash:
1) second swarm arives in mission 2
2) flying around the meteor base in mission 2
3) watching the boch guy escape in mission 3
4) freighters are ariving in mission 3
5) the capital ship thing is coming to help in mission 3
im using the -nohtl command becuz my card doesnt support it.
my card is the equevelent of a geforce2 GTI (but it isnt nvidia or ati)
im using all the media VP's exept the HI effect one. becuase it says it will slow it down.. also.. if i dont use the media vp or i try to play vinilla.. then it shows a white screen at start and it just stays white...
NOTE: i hate random...
NOTE2: with the -nohtl thing i had to set my gamma to 1.8 bucuase there was no lighing on ships and they apeared black as the sky behind them...
-
try it with -htl, -htl will use software rendering if it needs to, but it will be faster regardless.
What are the exact specs of your computer? Name of the video card, processor, memory, operating system, etc.
Do you by any chance use the 'target ship in reticle' command just before you crash?
-
AMD duron 1.6
256mb kingston (2.5.5)
sis741 (integrated 64mb@200mhz)
windows XP SP1
what is the target in reticle command.. i dont know what it is...
NOTE: as i said.. my card doent support htl and will cuase lockups when anything that uses it is fires (for now only the beams on ships cuase lockup)
also.. the part of the mission i could play with htl on looked better.. but the frame rate was still the same 30-60 fare
-
By default the target in reticule command is Y, it targets the ship in your reticule. ;)
-
Originally posted by nall
AMD duron 1.6
256mb kingston (2.5.5)
sis741 (integrated 64mb@200mhz)
windows XP SP1
what is the target in reticle command.. i dont know what it is...
NOTE: as i said.. my card doent support htl and will cuase lockups when anything that uses it is fires (for now only the beams on ships cuase lockup)
also.. the part of the mission i could play with htl on looked better.. but the frame rate was still the same 30-60 fare
HT&L is used for everything, except for the jumpnodes. Are you using any non-standard data (media VP, high poly models)?
-
im using all the media vp as said above.
If i remove a media vp file from the directory does it stop using it?
... im thinking these random crashes may have to do ALL with explosions. I figured out that the freeze with htl is cuased by explosionsnot by beams. (i blew up a friether to test this and it froze)
im thinking maybe the CTD is the same.. but like a -nohtl version.. so it crash instead of freeze?
(if so maybe i can remove the media vp for explosions.. wich one)
-
All the media.vp files are optional. You can remove any or all of them as you choose.
-
ok i found it is completely random..
i just played for 2 hours straight using the old speak build.. failed a mission.. the it crashed at the end of loading screen...
-
you could use more memory.
HTL will work wether you have a card that suports it or not, if you don't DX will emulate the feature, everything will still be faster, but more importantly we realy arn't working that hard to mantain the non-htl code path, it oftine times gets screwed.
-
im not sure how many times i have to say that your htl code is very buggy. DX "cannot" emulate it with your current code. this means that older cards that dont support it wont have a choice in using it or not.
2 more crash
training mission - demos class thing is wraping in
biggining of mission with some shivans
these are truly random.. i have recreated these a few times and nothing crashes.. it must be some major bug in your DX code
also when trying to run OGL it says to upgrade to 1.2
im guessing i only have 1.1 and guessing my card dont support 1.2 or something...
-
No, it means you need to upgrade your software to 1.2, by downloading some patch.
Also, when you do use HTL, when EXACTLY do you crash? Only when a ship fires a beam, or at other points as well?
-
if it isn't being emulated it's either direct x or your card's driver thats at fault, it works great with a number of older cards that don't suport HT&L.
-
http://www.hard-light.net/forums/index.php/topic,23601.0.html
this is the same problem.. at first i WE both thought the problem was beams.. this is not the case.. it is explosions of big ships.
the reason for thinking it was the beam is becuz it freezes right when the beam hits the ship and cuases it to explode.. however... ive tested this on another level where i personaly detroyed the frieghter and it freezed on explosion.
there must be something screwy with the explosion htl or something...
NOTE: another 6 randfom crashes with the -nohtl flag.. ive got in the habit of just pressing run again and not taking anymore notes.. as the crashes seem to have nothing in connection
NOTE2: i just had 3 crashes in a row wile looking at the exact same cap ship (first mission with the kings)
NOTE3: looking at the finris with the media packs makes CTD
-
Just a suggestion... try removing the hipoly Fenris or the hipoly model VP. If you're not using HTL, then these will cause FS2 to go belly-up.
-
might it be the 3-D shockwaves? check if you get the same problem when a bomb goes off. No I dont realy know what I'm talking about, just trying to lend a hand.
-
well i found out that the old 12-5-2003 build works stable.. unfortunatly it must be REALLY old becuz it doesnt support any of the lines.. even -glow doesnt work...
-
Actually, up until late January, Glowmaps were activated by default... same with specular lighting, so the -glow tag isn't needed. Also IIRC, HTL WASN'T on by default, requiring -htl tag to activate, so if you're not wanting to use HTL, then you don't need to use the -nohtl tag.
Later!