[MarloMan]

Ok, new problem.

I type in my name in the pilot creation screen and press enter. When I do that, the game closes itself. What the heck is up with that? I have the Game of the Year Edition, meaning it's version 1.2. I downloaded and installed the patch again just to make sure, but that doesn't help.  The error log says that FS2 caused an Integer Divide by Zero.


First I can't even find the game; then I finally do find it I can't install it; and then when I finally figure out a way to install it this happens...

[Setekh]

I can't think of the problem.. hopefully someone else can...

[aldo_14]

Hmm...what are you entering as your name?

I'm trying to figure out where it gets the '0' value from, not sure.  

I've uplaoded my data info to http://www.3dap.com/hlp/hosted/reciprocity/Single.zip

The contents of this file go into data/players/single folder.  This should allow you to select my name & progress as an existing pilot, so try this and see if it works.

one thing - don't try to go into the barracks- because I've been using a bunch of mods -  and this will possibly crash FS2 (from the stored names of the ship types killed).

[MarloMan]

First I just entered "Marlo,"  then "MarloMan."  None worked.  Then I used your pilot and was able to get past that pilot creation screen.  I went to the barracks to see if it would crash and thankfully it didn't.  I tried creating a pilot from there with "Superman," and once I pressed enter, I was taken out of the game.

And to add to the long list of problems I've been having with this game, I noticed a lot of lines making a grid on the screen.  Anyone know what that's all about?


Thanks a whole lot for your pilot file, by the way.

[Unknown Target]

What's your system specs?
And, BTW, you really didn't have to make this a poll, too

[Kamikaze]

This is one of the strangest technical cases I've seen so far, hope you find the problem soon

[MarloMan]

These are my specs:

Compaq 4090US
Windows XP Professional
900MHz AMD Duron
384MB RAM
SoundMAX Integrated Digital (IRQ 10)
GeForce 4 MX 440
Philips CDD4801 CD-R/RW 8X
Microsoft Intellimouse v4.01
25.2GB UltraDMA Hard Drive (3.71GB currently available)


Interplay support wasn't much help.  Despite me telling them that I have the Game of the Year edition, their solution for me was to update to version 1.1, meaning dumb my game down from 1.2.  It was an automated response, of course, so I doubt anyone read that part.


After using aldo_14's pilot file, then cloning it, then making it into a multiplayer pilot, then re-making it into a single player pilot I've found that the same thing happens whenever I try to view all available campaigns or when I select the mission simulator in the tech room.   I cloned his pilot, renamed it, converted it to multiplayer, then converted it back to single player to erase the stats, and it still happens so it's not because of anything missing from my game that he had on his.

[StratComm]

one thing - don't try to go into the barracks- because I've been using a bunch of mods - and this will possibly crash FS2 (from the stored names of the ship types killed).

The stats shouldn't matter; I have noticed that they correlate to the order of the ships in the tables, not the names .  When you change mods and look at stats; some of the kills by ship type get out of whack.  I played with a minor mod a while back, and now the counter has me down for 5 sathanas juggs (which I know is impossible) and a colossus or two.  Wierd, but true.

[StratComm]

What country are you in?  Could it have to do with the keyboard settings or something like that?

Also, what works in the game?  The main hall?  The Tech Room (ships, weapons, info)?  The Barracks you said did.  What about the campaign?  Pressing enter anywhere?

And for those who have had freespace 2 longer than I have, could it be a problem with the .vp file that is causing the error?

[MarloMan]

I'm in the United States.

As far as I can tell, everything but the Mission Simulator in the Tech Room and Campaign Viewer works.  I can start the training mission, but so far I wouldn't know what happens when I complete it.

Pressing enter anywhere else at any time other than after typing in the name of a new pilot doesn't do anything.  What was odd, though, was that when I cloned aldo_14's pilot I was able to type in a new name with no problems.

[karajorma]

Originally posted by StratComm


The stats shouldn't matter; I have noticed that they correlate to the order of the ships in the tables, not the names .  When you change mods and look at stats; some of the kills by ship type get out of whack.  I played with a minor mod a while back, and now the counter has me down for 5 sathanas juggs (which I know is impossible) and a colossus or two.  Wierd, but true.

I`m guessing that the stats DO matter. Take this senario as an example. Suppose FS2 has 40 ships. You play a mod which has 43 ships in. You then go back to the normal version of FS2. When you attempt to look at the kills FS works its way down the table until it gets to ship number 41. Then it gets confused. It's got records that you killed ships of that type but it can`t find that type on the ships.tbl. As far as it can see there are only 40 ships in the game. So it crashes.

[StratComm]

Originally posted by karajorma


I`m guessing that the stats DO matter. Take this senario as an example. Suppose FS2 has 40 ships. You play a mod which has 43 ships in. You then go back to the normal version of FS2. When you attempt to look at the kills FS works its way down the table until it gets to ship number 41. Then it gets confused. It's got records that you killed ships of that type but it can`t find that type on the ships.tbl. As far as it can see there are only 40 ships in the game. So it crashes.

that's true.  It's just never caused that sort of problem for me.

[karajorma]

Guess you haven`t played the wrong sort of mods then

[MarloMan]

How long before Interplay stops sending over automated messages?  Will it eventually end or is it always gonna be automated?

By the way, I fixed the grid problem by turning anti-aliasing off.

[Rampage]

I would worry about Windows XP, AMD Duron, and GeForce4.  Windows XP isn't compatible with some games.  I have heard people with XP can't run Freespace, but some can.  GeForce make sure that you have the latest drivers (I assume so because GeForce4 is new.)  I personally don't like AMD (Good for overclocking though).

Also make sure that you quit all programs running in the background and/or taskbar items such as anitvirus programs, task manager (disable it), and the internet.  After eradicating taskbar programs from memory and Freespace 2 still crashes, hit ALT+CTRL+DEL (Windows 98, not sure for XP) and close all programs except explorer, systray, rundll32, and stimon (Again, not sure for Windows XP)

Try the items listed above.  If it still doesn't work, I can't help you.

[Galemp]

Just read the poll results; nobody wants to help you.
My All-Purpose Solution to Everything (TM) : Reinstall Freespace 2 completely.

[MarloMan]

Also make sure that you quit all programs running in the background and/or taskbar items such as anitvirus programs, task manager (disable it), and the internet. After eradicating taskbar programs from memory and Freespace 2 still crashes, hit ALT+CTRL+DEL (Windows 98, not sure for XP) and close all programs except explorer, systray, rundll32, and stimon (Again, not sure for Windows XP)

Doesn't work.  Interplay support told me to do this.  I told them it didn't work.  So far no response from them.

Just read the poll results; nobody wants to help you.  
My All-Purpose Solution to Everything (TM) : Reinstall Freespace 2 completely.

I've done that many, many times.



This is a very weird problem.

[Admiral LSD]

Originally posted by MarloMan
Doesn't work.  Interplay support told me to do this.  I told them it didn't work.  So far no response from them.

Of course not, many, if not all, of those modules are Win9x specific, they don't exist on an NT system.

One thing you might like to try is to go hunting through your Event Log for stuff around the time FS2 crashes. The Event Viewer is located in the Administrative Tools section in either your Start Menu proper, the Programs section of the Start Menu or the Control Panel.

[Ulundel]

Originally posted by Rampage
I would worry about Windows XP, AMD Duron, and GeForce4.  Windows XP isn't compatible with some games.  I have heard people with XP can't run Freespace, but some can.  GeForce make sure that you have the latest drivers (I assume so because GeForce4 is new.)  I personally don't like AMD (Good for overclocking though).

Also make sure that you quit all programs running in the background and/or taskbar items such as anitvirus programs, task manager (disable it), and the internet.  After eradicating taskbar programs from memory and Freespace 2 still crashes, hit ALT+CTRL+DEL (Windows 98, not sure for XP) and close all programs except explorer, systray, rundll32, and stimon (Again, not sure for Windows XP)

Try the items listed above.  If it still doesn't work, I can't help you.

I think that XP is the problem. I have almost same thing - fs crashes sometimes in some X place (briefing, ingame) but at least I can play it.

[IceFire]

Try not pressing enter.  Use DA MOUSE!

No really, type your name in and use the mouse to enter.  Make absolutely certain that no MODs are installed and give it a try.  It does not sound like an OS issue at all because there are plenty of people running FreeSpace on all versions of WindowsXP with no problems at all.  FreeSpace 2 on XP Home on my machine works better than it did under Win98SE.