Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: procdrone on November 08, 2014, 10:30:15 am
-
Hello there, I am having a bit of tricky problem here.
Whenever I am facing a beam weapons fireing, my game crashes. (doesn't occurs when looking elsewhere, or on debug build, so I am having problems with nailing the cause).
Actually I am using "Intel(R) HD Graphics 4000" running on latest drivers, on 3.7.2 RC4 (no nightly build, just the stock 3.7.2 RC4 one.)
should I post the fs2open.log regardless? Any ideas?
-
Always post the log.
There have been a couple of reports of this lately with the RC4, can you try the latest nightly to see if the issue repeats? and report back which which nightly version(s) you use and what if any difference it makes
-
Alright, so here we go.
I've run a tests on following builds:
FS2 Open 3.7.1 (Build 11170) (normal-crash, debug-running /.log attached)
FS2 Open 3.7.2 (RC4) NO SSE (normal-crash, debug-running)
There is completely no difference, with what build I use, in both cases the normal ones crash, and debug ones run normal.
[attachment kidnapped by pirates]
-
Well, I can't reproduce this so far using r11170 or r10721, on Linux with a GTS 450, playing "King's Gambit" with mediavps_2014. Can you try this mission to see if you experience the crash when playing it?
-
The King's Gambit running just fine. Completed the mission without any problem.
However, my missions still make me crash out, making testing missions a real pain.
-
Do you have custom beams perhaps?
-
I do, but I don't believe its problem of custom beams, becouse my beta-tester have no problems like this, moreso, crashes are occuring with regardless if stock ones, or mod ones are in use.
-
Can you recreate the crash with a mission using nothing but retail assets?
-
Yes. That's what my mission practically is - using only MediaVPS-2014 assets (spare for the skyboxes), I am getting crashed out.
Should I attach the mission?
-
Yes.
-
There you go, file attached.
I only took out SEXP's for music changing and skybox changing, so there will be no warnings up.
[attachment kidnapped by pirates]
-
And when does that mission crash for you?
-
Practically at the start, i hear a first muzzle sound for Sathanas Beams, and when a beam is supposed to be fired... crash.
-
Given that you have an Intel HD 4000, does anything change if you use -no_glsl? If not, can you try the mission with this build (http://www.hard-light.net/forums/index.php?topic=87121.msg1768556#msg1768556) and see if it still crashes?
(Just trying to generate some extra information here, since I can't reproduce the crash either.)
-
Well, im forced to use -no_glsl or else, missions won't even start up, as for the build you've proposed, im getting it checked right away.
-
Oh, I only just noticed the -no_glsl in the debug log. I'm honestly expecting that this is related to the video drivers in some fashion.
-
Maybe be, when i was trying out different flags, i noticed that i can somehow "prolong" the time before the crash occurs.
As for the build you advised, FS2O wont even start with it.
-
Just a heads up, but your drivers are over 18 months out of date. Current base version is 15, not 9 as seen from your log. Update your drivers for the ability to use glsl, just keep post processing off as it can be an fps killer.
Strange how this doesn't happen on my laptop (also an HD 4000) or my desktop. This appears to be a very finicky bug.
-
...outdated... 18 months...? WTF, I am sure i've downloaded patches... less then month ago O.O
anyway, ill make sure to download the latest drivers, and see what is going on...
-
Did you download a driver specifically for the HD 4000? Intel has stopped making video drivers for each iGPU in favor of a single, unified driver for everything from the Intel HD Graphics basic to the Iris Pro 5200. Although you have to be on Win 7/8/8.1 to use the latest drivers now.
Here is the 64-bit link(released 23 of october): https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24329
-
Instalation said that the drivers you gave are not appropriate for this computer... dunno...
EDIT
Yea, i use a dedicated drivers for iGPU as you named it.
-
Hmm indeed. I've dealt with this before. Download the zip, extract all the contents to a folder and run the setup file found within. Tends to work better than the exe at times.
What cpu model do you have? Are you using Windows XP and/or a 32-bit OS?
-
Both ways do not work for me.
I might.... done a TERRIBLE mistake, and looked up a wrong entery up my device menager... under display adapters, i have listed:
-Intel(R) HD Graphics 4000
-NVIDIA GeForce GT 720M (which should be my grahpics cart)
i still have no clue why i wrote otherwise in the first place...
As for my CPU: Intel(R) Core(TM) i3-3217U CPU @ 1.8GHz listed x4.
-
Ah, ok. Now, we need to figure out why FSO is not running on your 720M.
-
It won't. :headdesk: I'm in the same boat. (To try, you can open nVidia control panel, find FSO .exe, and set it to use the nvidia high performance instead of intel, but FSO will happily ignore that and only use the intel, at least for me).
-
Maybe the log after the graphic drivers update will help...
but ill try what jr2 proposed
[attachment kidnapped by pirates]
-
No dice, drivers are the same version as before. Go to the Display Adapters in the Device Manager and click update drivers on the HD 4000, then tell it to look on the computer and see if there is another version laying around somewhere.
-
jr advice didnt worked, but at least i can run missions with glsl turned on, it crashes out now on the second scene, just about as all the ships are about to fire.
-
........ and i managed to get it working properly!
I've set flags for higher quality (lighting, aliasing, soft particles etc.) ... and it worked without any problems.
-
hmm? What did you do to get it working? Were you able to download newer drivers?
-
........ and i managed to get it working properly!
I've set flags for higher quality (lighting, aliasing, FXX, soft particles etc.) ... and it worked without any problems.
Wrote it.
-
Well, that's unusual... I think. I've never heard of a situation like that.
-
It won't. :headdesk: I'm in the same boat. (To try, you can open nVidia control panel, find FSO .exe, and set it to use the nvidia high performance instead of intel, but FSO will happily ignore that and only use the intel, at least for me).
that might help you.
https://www.youtube.com/watch?v=Zh4HCadTY_A (https://www.youtube.com/watch?v=Zh4HCadTY_A)