WolfK33 Posted May 5, 2013 Posted May 5, 2013 Hi, first thank you so much for this Huey Belsimtek, a dream since earliest C116 and C64 times finally came true! Absolutely outstanding work ! :thumbup: Now on topic: I encountered a weird problem in the second UN-Campaign mission: After mission start, without moving the chopper I went to F2-view and without changing the camera angle I turned on the anti-collision light (the red one on top). Exact steps were: Start mission, turn off yellow text, center TrackIr, zoom neutral, F2, a-c light on. After about half a rotation of the light my screen went white, the sound stopped and my PC stopped responding completely, had to do a hardware-reset. I tested this several times with the same results. Then I started up the mission but turned the camera to the other side of the chopper and then turned on the anti-collision light. The screen went white again, but the sound stayed on, but somewhat "stuttery", then after some seconds the screen turned black, then the sim was back, but with fps in the single-digit area. Turning the anti-collision light on and off changed nothing then, no more white screens but still extremely low fps. Then I went to the mission editor and tested with various aircraft skins on airports as well as farps in different camera angels: No problem with the anti collision light. I then started the second campaign mission again -> F2 -> light on -> "White screen of Death"... :alien: Now I´ve no idea if this is a problem with my computer or with the sim, maybe some special combination of light settings (early morning) and skin and lights or whatever, but I thought I´d post it here... My PC is a i7-3770 with 16GB, Win8 64, GeForce GTX 660 Ti Greets, Wolf
WolfK33 Posted May 13, 2013 Author Posted May 13, 2013 Yesterday I started up campaign mission 8 (I think that´s it, where you defend the checkpoint that´s under attack at night) and had the same thing happen, but without the anti collision light. External view -> Boom, white screen, complete computer lockup. Retried several times with the same results. I´ve flown other missions at night time or dusk/dawn and all went well, it only happens in the campaign missions, so it really seems it has something to do with the white spanish UN skin and those times of day. I don´t say there´s something wrong with the skin, probably it´s something on my end, but nowadays I have no idea anymore about all that computer stuff unlike when I was young... :cry:;) Windows gave me some .dmp file it wants to automatically send in to look for the problem (no results), but it seems I can´t attach that here...
71st_Mastiff Posted May 13, 2013 Posted May 13, 2013 Yesterday I started up campaign mission 8 (I think that´s it, where you defend the checkpoint that´s under attack at night) and had the same thing happen, but without the anti collision light. External view -> Boom, white screen, complete computer lockup. Retried several times with the same results. I´ve flown other missions at night time or dusk/dawn and all went well, it only happens in the campaign missions, so it really seems it has something to do with the white spanish UN skin and those times of day. I don´t say there´s something wrong with the skin, probably it´s something on my end, but nowadays I have no idea anymore about all that computer stuff unlike when I was young... :cry:;) Windows gave me some .dmp file it wants to automatically send in to look for the problem (no results), but it seems I can´t attach that here... you dont have a crash log in your user\saved games\dcs folder? "any failure you meet, is never a defeat; merely a set up for a greater come back", W Forbes. "Success is not final, failure is not fatal, it is the courage to continue that counts", "He who never changes his mind, never changes anything," Winston Churchill. MSI z690 MPG DDR4 || i9-14900k|| ddr4-64gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || Z10 RGB EVGA Keyboard/ G502LogiMouse || PiMax Crystal VR || 32 Asus||
71st_Mastiff Posted May 13, 2013 Posted May 13, 2013 well to tell ya I have some buddies having the same issue withthis game and they have Ti cards allso, not to say its a bad card but lighting issues seem to make them either crash or BSOD only on this game..:joystick: "any failure you meet, is never a defeat; merely a set up for a greater come back", W Forbes. "Success is not final, failure is not fatal, it is the courage to continue that counts", "He who never changes his mind, never changes anything," Winston Churchill. MSI z690 MPG DDR4 || i9-14900k|| ddr4-64gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || Z10 RGB EVGA Keyboard/ G502LogiMouse || PiMax Crystal VR || 32 Asus||
WolfK33 Posted May 13, 2013 Author Posted May 13, 2013 In that folder there´s autoupdate.log dcs.log dcs_frame.log debrief.log inputscript.log me.log net_server.log Mmh, great, I just bought the computer new, mainly for this sim, of course it has a card that doesn´t like DCS... So probably no UN-flying for me at night anymore...
71st_Mastiff Posted May 13, 2013 Posted May 13, 2013 In that folder there´s autoupdate.log dcs.log dcs_frame.log debrief.log inputscript.log me.log net_server.log Mmh, great, I just bought the computer new, mainly for this sim, of course it has a card that doesn´t like DCS... So probably no UN-flying for me at night anymore... what drivers you using, playing with those might help? "any failure you meet, is never a defeat; merely a set up for a greater come back", W Forbes. "Success is not final, failure is not fatal, it is the courage to continue that counts", "He who never changes his mind, never changes anything," Winston Churchill. MSI z690 MPG DDR4 || i9-14900k|| ddr4-64gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || Z10 RGB EVGA Keyboard/ G502LogiMouse || PiMax Crystal VR || 32 Asus||
71st_Mastiff Posted May 13, 2013 Posted May 13, 2013 (edited) i'm running 314.22whql no isues with my card.. try running 2nd pic try it with the texture filtering-trilinear optimization on and off Edited May 13, 2013 by Mastiff 1 "any failure you meet, is never a defeat; merely a set up for a greater come back", W Forbes. "Success is not final, failure is not fatal, it is the courage to continue that counts", "He who never changes his mind, never changes anything," Winston Churchill. MSI z690 MPG DDR4 || i9-14900k|| ddr4-64gb PC3200 |zotac RTX 5080|Game max 1300w|Win11| |turtle beach elite pro 5.1|| ViRpiL,T50cm2||MFG Crosswinds|| VT50CM-plus rotor Throttle || Z10 RGB EVGA Keyboard/ G502LogiMouse || PiMax Crystal VR || 32 Asus||
WolfK33 Posted May 13, 2013 Author Posted May 13, 2013 I just looked, driver 311.06 , probably should update that. PC is still as it came from the store with just Arma2, DCS and TrackIr-software installed... Thanks for the help, I´m gonna play around with those options when I have the time.
WolfK33 Posted January 28, 2014 Author Posted January 28, 2014 (edited) By the way, this problem is still there. I have the newest drivers in the meantime, also trilinear optimization on/off made no difference. With the Huey and night missions when I go to external view I immediately get a black, yellow, white or some other color screen and have to do a computer reset. When staying in cockpit it lasts longer, sometimes I can even fly without the computer crashing. No DCS crash log... Hmm I guess it´s either save for a different card or daytime flying only... :-( edit: it´s not just the UN skin. Edited January 28, 2014 by WolfK33
WolfK33 Posted January 28, 2014 Author Posted January 28, 2014 Hi again, only a few hours later I think I can report this problem solved ! I spent the whole day searching the internet for this problem again and this time found several threads where people had a similar problem with this card in other games. I read that many 660 TI cards come from manufacturers slightly overclocked which could lead to such problems. So I downloaded according to a "tutorial" in such a thread a program called nvidia inspector which shows and lets you change all such stuff that is usually too much for me ;-) And yes, my gpu ran at 1006 instead of the 915 mHz that nvidia says, the memory at 3054 instead of 3004 mHz. I lowered both values to what nvidia writes, fired up a mission that always locked everything up half a second after pressing F2 and it worked ! I didn´t fly so far (not much fun with the arm in a cast...) but I could happily pan the external cam around and finally see my huey in the dark ! I hope it stays that way and that by lowering it´s now not too slow. Thanks all for your help ! :joystick::pilotfly:
Recommended Posts