Author Topic: Installation FSOpen  (Read 1693 times)

0 Members and 1 Guest are viewing this topic.

Installation FSOpen
Hi Guys,

first of all thank you for your work und sry that I may steal your time!
I have major troubles to get run my copy of FS2 Open. (I'm usinng Win 64 Bit)
I'm using no downloaded or illegal version of FS2, but a (german) version of the german games magazine "Computer Bild Spiele" which sold FS2 in their magazines-DVD in an issue back in 2006.
Until now I've intalled that version and the basic setting from the FreeSpaceOpenInstaller, which I've downloaded today.
But whenether I try to run the game (no matter if i try to run the fs2_open_3_7_2_RC3 or with the wxlauncher or with the launcher from the installer) there's a popup that says:

strings.tbl(line 4226):
Error: Expecting int, found [; ------------------------------------------------].

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>

If I try to run FS2 without any mods or graphical updates, the RAM-problem occurs, which is described in your FAQ.
Does anyone know this problem and is able to help me?
I would be so glad!

Greets,
Hannes
 

 

Offline DahBlount

  • 29
  • Alpine ☆ Cancer Tribulation
    • Minecraft
    • Skype
    • Steam
Re: Installation FSOpen
That is indeed unusual, FSO should not be trying to read through a commented section. Have you tried using the MVPs 2014? It may fix the problem you are having.

I've heard of this problem before but I can't remember the exact way it is fixed. Hopefully someone with more experience will come by with a proper fix.

Another good way to help us: Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.
<Axem> yet still more insightful than #hard-light

<Axem> jad2.23 will just be cat videos

<DahBlount> So
<DahBlount> JAD2.2 is like that
<Axem> maybe
<Axem> it can be whatever you like!
<DahBlount> A Chocolate Sundae?
<Axem> sure

My models: GTF Gilgamesh - GTD Nuadha [Redesigning] - Ningirama [WIP] - GTG Zephyrus

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Installation FSOpen
This is a known bug with the German and French tables which was only recently exposed by corrections to the parsing code; it will hopefully be fixed in 3.7.2 RC4.

EDIT: The Mantis issue in question, if you want to follow its progress.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 
Re: Installation FSOpen
Thanks for your quick answers! :D
Quote
Have you tried using the MVPs 2014?
Yeah I have. There's a option in the wxlauncher to activate the MVPs 2014.

@AdmiralRalwood:
Thank you! Is there anything I can do to help you/the other guys to fix this problem?
For example posting my fs2_open.log file (after i've learned how to create one^^).

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Installation FSOpen
Is there anything I can do to help you/the other guys to fix this problem?
For example posting my fs2_open.log file (after i've learned how to create one^^).
A debug log would not be particularly helpful; the problem is well-understood, it's all a question of how the solution should be written at this point.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.