[WMCoolmon]

• Begged for by WCS: Bumped personas limit to be the same as an Inferno Build
• Requested by Kuras: Targeting reticle takes lag into account in MP
• Asked for by some multiplayer guys: -mpnoreturn removes the return to flight deck option on respawning

Let there be a great feast, and much rejoicing

Oh, it's all untested...couldn't find any multiplayer servers.

[Kuras]

thx WMCoolmon )

[Tolwyn]

Originally posted by WMCoolmon

• Begged for by WCS: Bumped personas limit to be the same as an

[/B]

Coolmon, you are the man :) Thanks alot.

//starts to hack messages.tbl into pieces :)

[Svizel]

This build seems to work ok, -mpnoreturn works perfectly and i didnt find any serious bug yet. I just noticed mission loading time increased rapidly even with -jpgtga, -pcx32 and large textures disabled, but i think it's cauase i also installed mv_textures_c.vp. I'll do few more tests today.

[Bobboau]

what was the build you are compareing loading times with?
index buffers require massive amount of thinking to generate

[Tolwyn]

what's the new personas limit, btw?

[Svizel]

I was comparing it with fs2_open_C07122004.exe, but as i posted i'm not sure if huge loading times are because of new build or new textures. I'll post more info tonight...

[Charismatic]

The thing won’t start up; all it does is flash for a bit then returns to desktop. No error boxes, no 'need more virtual memory' boxes, nothing out of the ordinary comes up.

The version and command flags I use are: C:\Games\FreeSpace2\fs2_open_C07202004.exe -mpnoreturn -safeloading

And I have the mv_core_b
...
Can anyone help me out with this problem? I have a Windows XP Home edition, and the last time I installed the FS2_Opean launcher, it didn’t work after one try, it crashed and froze when I got 1\2 through loading a mission. That was the farthest I got, with the .DLL things not working and 'virtual memory' boxes.

By the way, some times when I start up the launcher, this box comes up:
'WARNING!'
'Unrecnoized command line paramater -get_flags, continue?'
or 'Fatal error' all talking about flags, or wrong\missing flags.

Does this mean anything to you guys?

[Svizel]

I made quite a few tests and this loading problem is not cause by this build version, since it would be offtopic here i posted more info here.

[Singh]

Hmm
this may seem odd, quite contradictory to what I posted before, but I think I found a method to improve FPS drastically.
I switched off the 'use large textures' box in the launcher, and after that my load times cut in half, and FPS doubled, almost tripled even. This was with all jpgtgas off, but remarkably, with the zpack I get pretty good performance with the new anis and explosions!

Can anyone else confirm this?

[Charismatic]

Thank you Svizel, ill try it. Maybe it will fix my FS2_Opean problem. On another note, does anyone have any suggestions on how to solve the other problem?

"The thing won’t start up; all it does is flash for a bit then returns to desktop. No error boxes, no 'need more virtual memory' boxes, nothing out of the ordinary comes up.

The version and command flags I use are: C:\Games\FreeSpace2\fs2_open_C07202004.exe -mpnoreturn -safeloading

And I have the mv_core_b
...
Can anyone help me out with this problem? "

[WMCoolmon]

You MUST run fs2_open from the Launcher...I'm guessing that you haven't selected the EXE. Try clicking the "browse" button in the upper-right of the launcher and select the EXE you want to use. Check the features tab, this will have a descriptive list of all command lines; you might have to restart the launcher to see them.

Skip down to the "Configure the Launcher" section of this page for more detailed info: http://dynamic4.gamespy.com/~freespace/fsdoc/index.php/Downloading%20and%20Installing

[Charismatic]

I did select the correct version of FS2_Opean. So it’s not that.
Any other thoughts?

By the way, IN the video area, at first I had the Direct3d8 thing. I just selected the other one, the one with the O. Anyway, I get a flash of the starting screen of fs2, when I run it, but then it breaks down and says some buffer overrun corrupted the internal stuff of the FS2_Opean. Every time I use the one with the O, I’m one step closer, cause I saw the starting screen for a second, but also a step farther, the buffer overrun thing.
Any ideas on how to fix the overrun?

[xenobyte6666]

nice build, the opengl works too , major plus that - cos i can alt-tab without fs2 going splat now.

found one bug tho, when i hit f2 when in a game or on the server list screen fs2 crashes to desktop or the options screen comes up with just the names of stuff, no background or buttons.... and then crashes to desktop.

strange bug that, otherwise this build works good thanks

[xenobyte6666]

hmm it just ctd'd in multiplayer just as was launching into RI , had just played RI fine tho.

Was using opengl, with latest vp's including effects one.

weird.

[xenobyte6666]

more bugs found im afraid, sorry im not using mantis, but am in a hurry and not got time to faff with it atm.
will try mantis next time

ok have found a major openGL problem, in multiplayer it crashes to desktop at the start of the second mission played - dont matter whether hosting or a client . It happens every time - dont matter which mission you do.

Nother bug was just found while playing doomsday mission, all the ai fighters froze 3/4 through the mission, the models disappear and when u target then it points you to the top left, but the red arrow thing always stays in top left and end up spinning round never finding target ship cos it disappeared but still targeting.... - this only happened with direct3d.

[taylor]

xenobyte6666: Try to create a new pilot and see if you can reproduce the F2 crash problem.  If you can I've got a debug build I'd like you to try  (http://icculus.org/~taylor/fso/testing/20040720-win32-debug.zip) and see if it gives you some extra info.  You may want to run the debug build in a window or else it will switch back and forth as warning messages appear.

For the crash on second mission problem please try using the -novbo command line option.  It's under Troubleshoot in the Launcher (Disable OpenGL VBO).  If this fixes the problem for you please let me know what graphics card you have and what driver version you are using.

[Charismatic]

Anyone have an answer to my earlier problem, I see many are being solved but..

[xenobyte6666]

hi i used that debug, build with windowed mode, and the -novbo command line option, was running with the all features on thing as well, in opengl mode.

the good news is that it hit f2 in mission a few times and it didnt screw up this was with a new pilot file.

the bad news:

First bug was halfway through allalone, respawned and found that everything was spinning and i had no control - so had to end mission. so went and tried another mission and it crashed on second mission again was trying a dogfight one this time and it dont seem to matter which mission it is. - with a new pilot file, it hangs on the screen just before entering actual mission.
It comes up with the microsoft error , program is not responding thing and asks if i wanna do an error report. And meanwhile the program continues to eat RAM i think it got to 420,000k of memory used by the fs2 exe file before my pc crashed.

i can send u the errorlog.cfg and the fs.log files if you want them - give me an email address, or msn, or icq, or irc.

I use a gainward geforce fx5900 128mb ddr
my basic pc specs are:

abit nf7-s nforce2 motherboard
amd 2500xp barton
2 x 512mb pc3200
geforce fx59000
510gb HDD Space on 250gb, 120gb, 80gb and a 60gb all maxtor
lite-on cdrw
lite-on dvd player
windows xp professional sp1 and all updates installed.
Nforce drivers version 4.24
Nvidia Display Drivers version 6.14.10.5672

let me know if you need those errorlog files.

[karajorma]

Originally posted by Charismatic
Anyone have an answer to my earlier problem, I see many are being solved but..

I'm getting the exact same problem. I've tried clearing the entire list of all custom flags and it's not doing me any good.

I'm running standard FS2_Open (no mods) with all the latest vp files.

Does this build require any of the changes that the earlier HUD changes builds required?