Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Kosh on March 02, 2007, 11:36:12 pm
-
Ok, here is what happened:
A couple of months ago my old laptop died. It just died, right in front of me. So I had to borrow another one from a friend of mine. Considering that uses an integrated Intel graphics card, and also that it only has 256 MB of RAM I decided only to use MV_Core.vp as well as the latest FSO build.
After setting everything up, I downloaded BR's new campaigns, as well as BR's version of Derelict.
I try to play all of them, and they all had an interesting problem. Eventually during the first mission, they would all CTD. For different campaigns it happens at different times, but it is consistent.
So I was really disappointed and thought I would un-install all of the mods, which I did successfully, and play normal FS2. But that had the same problem. What's the deal?
-
Which Intel IGC do you have? Only a few of them are supported, so that may be the issue right there. Also, what cmdline options are you using? There are known issues with certain things (such as -img2dds) and even the supported Intel cards.
-
What exactly happened to your old laptop.. I'm curious. Did it start spitting errors, just shut off, or what?
-
I'm only using the -fps and -mod flags, nothing else.
System information says 82852/82855 GM/GME
I know it can't handle OpenGL (as it had many missing textures), so I used D3D.
As for what happened with my old laptop, one day I was watching a movie, and then I got a STOP error. After that I turned it off, and then tried turning it back on. The power light would flash and then nothing. Definate hardware failure. It's dust.......
-
Hmph. You tried removing the battery and running it on AC, and visa-versa? That's the only thing I could think of. It seems to be in the power supply somewhere, as its not even trying to boot, and it is flashing the power light at you. (Instead of just turning it on.) Maybe a power surge got it.
-
Hmph. You tried removing the battery and running it on AC, and visa-versa? That's the only thing I could think of. It seems to be in the power supply somewhere, as its not even trying to boot, and it is flashing the power light at you. (Instead of just turning it on.) Maybe a power surge got it.
What I mean by "it's flashing" means it will be on for a millisecond and then it turns back off and then nothing else happens. No lights, nothing.
-
You know what the most irritating error is? THIS:
Error: Can't open model file <none>
File:J:\src\cvs\fs2_open_3_6_9.final\code\Model\ModelRead.cpp
Line: 1902
[This filename points to the location of a file on the computer that built this executable]
Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
I seem to periodicly get it and none of my home-made missions want to work.
-
Hmph. You tried removing the battery and running it on AC, and visa-versa? That's the only thing I could think of. It seems to be in the power supply somewhere, as its not even trying to boot, and it is flashing the power light at you. (Instead of just turning it on.) Maybe a power surge got it.
This happens on both AC and battery power, right? I figure the power source is fried or there's a short in the power supply. Did your AC cord have a sharp turn angle on it? I mean, was it always kinked to the side, from either too long distance or pushed against the wall? That might do it. What was the Make/Model of your laptop, anyways?
What I mean by "it's flashing" means it will be on for a millisecond and then it turns back off and then nothing else happens. No lights, nothing.
-
I don't believe it's a problem with the AC power or the battery because of the stop error just before this happened. When it tried to dump the memory, it couldn't even do that.
So, is my Intel "card" supported?
-
A test machine with an 855 works fine for me, except for the use of -img2dds, so I'm not sure what the issue might be. I have only tested it with OpenGL though, since D3D doesn't have any support from any of the devs and is too far out of date.
Make sure that you have to most up-to-date drivers (some notable bugs were fixed in the last release), give it a try in OGL, and let me know what doesn't work.
-
I'll try this weekend. My vacation just ended so I won't have any time to deal with it until then. :(