Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Platinum on October 02, 2008, 02:13:51 am

Title: So, probably not that that big of a deal,
Post by: Platinum on October 02, 2008, 02:13:51 am
But when I use the launcher with 3.6.9, it says that the "webcursor bitmap was not found".

It gives me three suggestions.  I have Freespace open in the folder, and I don't believe my freespace 2 is corrupted, as I was just playing it before i downloaded the newer version of open.

Any thoughts?  Point out something I've missed?
Title: Re: So, probably not that that big of a deal,
Post by: Jeff Vader on October 02, 2008, 02:28:26 am
So you've had FSO before and it has worked? If you're using shortcuts for the Launcher and/or the builds, make sure their paths are correct.
Title: Re: So, probably not that that big of a deal,
Post by: FUBAR-BDHR on October 02, 2008, 02:30:21 am
System specs?  By any chance are you using Direct3D?  If so switch to OpenGL.  You could also run the debug build and attach the fs2_open.log from the data directory. 

Man your fast Lobo.  He did say it was working before he downloaded a newer version of 3.6.9.

And you edit your posts fast too. 
Title: Re: So, probably not that that big of a deal,
Post by: Jeff Vader on October 02, 2008, 02:37:04 am
Man your fast Lobo.  He did say it was working before he downloaded a newer version of 3.6.9.

And you edit your posts fast too. 
Well, they don't call me the Problem Solving Wolfman for nothing.
Title: Re: So, probably not that that big of a deal,
Post by: Platinum on October 02, 2008, 11:47:09 am
So you've had FSO before and it has worked? If you're using shortcuts for the Launcher and/or the builds, make sure their paths are correct.

Everything is in my Freespace folder, and I'm not using shortcuts.  I believe I was using 3.6.7, but that was before I knew anything about computers, which was only about... two?  two years ago?  I feel like you've put it out sooner than that.



System specs?

Not fantastic.  I'm about to build a better computer in a month or two, so if necessary, I can wait until then.

Celeron CPU 2.8 GHz,  768 Mb of ram (i had a gb, but one of the older 256s burnt out), 120 gb hard drive, NVIDIA Geforce FX 5200, and I'm running XP professional.

By any chance are you using Direct3D?  If so switch to OpenGL.  You could also run the debug build and attach the fs2_open.log from the data directory. 

No, I'm using Open GL.  When i use the launcher to run the debug, it does the same thing.

He did say it was working before he downloaded a newer version of 3.6.9. 

Again, not newer version of 3.6.9, and old 3.6.7.  And now, when I try to run fs2 independent from FS Open, it crashes, and says it's experienced a problem and needs to close.
Maybe it corrupted somehow between the time I played it last, and the time I tried to play it post 3.6.9 + media vp downloads?

EDIT:  Also, I just tried to load my old 367 version of fs open, and it also thinks that it's being not being run from the same place i installed freespace.  What happened...?
Title: Re: So, probably not that that big of a deal,
Post by: FUBAR-BDHR on October 02, 2008, 12:30:47 pm
Try deleting the launcher6.ini file and rerun the launcher, do you setting, and try it again. 
Title: Re: So, probably not that that big of a deal,
Post by: karajorma on October 02, 2008, 12:53:20 pm
If that doesn't work do this.


http://homepage.ntlworld.com/karajorma/FAQ/installingfs2_open.html#upgrade

Don't delete anything or install anything but follow that guide on how to clean your FS2 folder. Then run FS2 retail. If that works, you can run the FS2_Open installer to get the rest. Otherwise post again and we'll try to solve the problem.
Title: Re: So, probably not that that big of a deal,
Post by: Platinum on October 02, 2008, 04:07:36 pm
Score.  I got it.  I had deleted all the "smarty" "stu" "tango" vps, because i had assumed they were old media vps that I didn't need.

I guess I did need them.  I think this'll work now, let me try it out.
Title: Re: So, probably not that that big of a deal,
Post by: chief1983 on October 02, 2008, 04:11:31 pm
You definitely need all the retail vps, and you should keep your mediavps inside a mod folder so that kind of stuff doesn't happen :)
Title: Re: So, probably not that that big of a deal,
Post by: Platinum on October 02, 2008, 04:17:49 pm
But, new problem.  All the models have lines over them, kind of like wireframes.  They all look like window blinds.  Plus, the missiles leave trails that look like.... tape?

EDIT:  Except the Herc 2.  Except, the targeting model, down in the corner has the lines over it.

MOAR EDIT: And the frigate in the second training mission.  That model works too.  But the drones, and, looking through the models in the tech room, nearly all the rest of the models have lines all over them.  the ones that work are

Ursa, Herc 1, herc 2, leviathan and fenris, triton, bes, nephyt, one of the turrets.... and that's about it.

Also, shielding is just black spots, and when something is on fire, it's trail is a bunch of checkered squares.

Is this a graphics card problem?
Title: Re: So, probably not that that big of a deal,
Post by: FUBAR-BDHR on October 02, 2008, 05:45:46 pm
Could be.  Try updating your video drivers and make sure you are using OpenGL not D3D. 
Title: Re: So, probably not that that big of a deal,
Post by: Platinum on October 02, 2008, 05:53:26 pm
Checked for new drivers, and apparently there are none.  Yeah, I'm using open gl, 1024x768, 32 bit, trilinear filtering.

Seems all in order...
Title: Re: So, probably not that that big of a deal,
Post by: Jeff Vader on October 02, 2008, 06:12:49 pm
Checked for new drivers, and apparently there are none.  Yeah, I'm using open gl, 1024x768, 32 bit, trilinear filtering.

Seems all in order...
Which build were you using? Some builds can cause the stripe issue with Nvidia cards. Try the Recommended build for Windows users in my signature.
Title: Re: So, probably not that that big of a deal,
Post by: Platinum on October 02, 2008, 06:33:07 pm
Checked for new drivers, and apparently there are none.  Yeah, I'm using open gl, 1024x768, 32 bit, trilinear filtering.

Seems all in order...
Which build were you using? Some builds can cause the stripe issue with Nvidia cards. Try the Recommended build for Windows users in my signature.

I am using 3.6.9, but after trying 3.6.10, (from the link in your sig), there seems to be no difference.  I still have the striping on most models.  It's almost as though the texturing WANTS to be there, but can't.  Because the Psamtik has the prettier lights, that deeper orange, and the transports kind of flicker like there should be more there, but it's though it just can't seem to manage.
Title: Re: So, probably not that that big of a deal,
Post by: Jeff Vader on October 02, 2008, 06:35:57 pm
Hmm. Just to be sure. You have these drivers (http://www.nvidia.com/object/winxp_175.19_whql.html) installed, correct?
Title: Re: So, probably not that that big of a deal,
Post by: FUBAR-BDHR on October 02, 2008, 06:39:17 pm
We're dealing with an upgrade from an old version so what MediaVPs do you have?  Do you get the same problem if you disable the MediaVPs? 
Title: Re: So, probably not that that big of a deal,
Post by: chief1983 on October 02, 2008, 07:11:09 pm
I'm still worried the install itself might be broken.  If he every did install mediavps or other stuff in the root folder it'll be hard to rule that out.  Where's one of those guides that says exactly what should be in the root folder?
Title: Re: So, probably not that that big of a deal,
Post by: FUBAR-BDHR on October 02, 2008, 08:12:48 pm
In Kara's FAQ link posted earlier in the thread. 
Title: Re: So, probably not that that big of a deal,
Post by: Platinum on October 03, 2008, 12:23:50 am
It was the graphics card drivers.  Installed new ones, and

...

 :o

Holy ****.


It's so pretty.

This may not be the end, folks.

But hopefully, my next question will end up being about a problem with a MOD.
Because I'm really itching to play some of these, they look amazing.
Title: Re: So, probably not that that big of a deal,
Post by: Platinum on October 03, 2008, 12:45:39 am
Okay.  Now the models work fine.  All the ships look real pretty.

But leaking exhaust, and shield's reactions to being shot are still black space.  the smoke from burning ships is still represented as black squares, and shielding shows up as black space.  And the trails left by missiles are yellow strips.
Title: Re: So, probably not that that big of a deal,
Post by: Jeff Vader on October 03, 2008, 04:44:05 am
If you have the 3.6.8 Zeta MediaVPs, make sure you have the appropriate patches (files beginning with mp-710_) as well.
Title: Re: So, probably not that that big of a deal,
Post by: Platinum on October 03, 2008, 01:31:23 pm
I downloaded all the recommended Media VPs from this post. (http://www.hard-light.net/forums/index.php/topic,46260.0.html)

I also got the advanced effect vps.  And those kind of helped as far as shield reactions go, and make the smoke sort of see through, and more smoke like.  shields actually show up as shielding now, but it's a super dark tint, and looks more like glass.
Title: Re: So, probably not that that big of a deal,
Post by: FUBAR-BDHR on October 03, 2008, 01:35:45 pm
Run the debug build and post the log. (data\fs2_open.log)  A screenshot would probably be useful too. 
Title: Re: So, probably not that that big of a deal,
Post by: Platinum on October 06, 2008, 07:11:45 pm
I don't know exactly how to retrieve a debug log, but when I ran the debug of 3.6.10, it minimized after trying to load up Surrender Belisarius, saying that there was a "inertial deadzone for the myrmidon".  I said yes to the debug question, and then it said that there was an error, and freespace needed to close.

Here's a big photo of the being on fire problem from the above mission:
(http://i44.photobucket.com/albums/f36/Fifthsector/1.jpg)
Title: Re: So, probably not that that big of a deal,
Post by: chief1983 on October 06, 2008, 08:06:09 pm
Yeah the currently released MediaVPs aren't quite compatible with the newest debug builds, but there should be a new set soon I believe.
Title: Re: So, probably not that that big of a deal,
Post by: Wanderer on October 07, 2008, 12:31:41 am
Chief... true, but he doesnt have to get further than to main hall with the debug build.



Do - for example - following:

Open the launcher, set the current build to point to a debug build.
Run the game, quit after you reach the mainhall/main menu.
Go to the directory where you have installed your copy of FreeSpace 2.
Go to the data directory.
Find file names 'fs2_open.log' within that directory and preferably compress (zip/7z/rar) it.
And when you post it, do not use the quick posting window, instead click for example on the 'reply' or 'preview' button. In the new page you should see 'Additional Options...' option, select it and then attach the newly made compressed file to the post.
Title: Re: So, probably not that that big of a deal,
Post by: Platinum on October 07, 2008, 11:43:03 pm
Yeah, not finding anything in that folder.  Ran it on debug, and there's nothing there.
Title: Re: So, probably not that that big of a deal,
Post by: Wanderer on October 08, 2008, 01:35:10 am
Hmmm.. try searching for a file of that name
Title: Re: So, probably not that that big of a deal,
Post by: chief1983 on October 08, 2008, 09:09:53 pm
It's been indicated in IRC that you may be running the MediaVPs without the most up to date patches.  The new set will hopefully be out very soon, so you can either get the 710 patches from somewhere on the forums or wait a bit longer for a shiny new fixed set.
Title: Re: So, probably not that that big of a deal,
Post by: Vasudan Admiral on October 08, 2008, 09:15:21 pm
The 710 patches are up the top of this thread: http://www.hard-light.net/forums/index.php/topic,39905.0.html

Alternatively, try using this absolute latest build (http://swc.fs2downloads.com/builds/WIN/fso-WIN-20081008_r4870.7z) with the 3.6.10 Beta MVPs. (http://www.hard-light.net/forums/index.php/topic,51229.0.html) The betas do have a couple of known problems, but we're not far off the next release now, which we're working hard to ensure is the most stable bug free set yet. :D