[Master_of_the_blade]

Yeah, I can do C++.
I never knew C++ also had objects.

Well objects is the point of C++, so I assume you meant to say that you "never knew C also has objects".

Sorry, I was a bit misleading, C by itself does not have objects.  Using a C++ compiler to write C like code is what I mean by "C with objects".

As I said, my C++ programming knowledge is student level, maybe I did not realize it.
Anyways, I'll learn as i come across more code.

Is there a way to disable the rippling effect in the engines in the latest nightlies? It doesn't make sense in space.

Because fighters with energy shields doing pew pew with super sci fi cannons and firing missiles that have higher payloads than your average nuke that barely dent an Orion while completely disobeying the newtonian laws do make sense right? 

Good point.

[Alan Bolte]

 

Tracked down the specific nightly that broke the launcher for me: 6170

There are quite a few changes from 6102 to 6170, so I'll leave it up to someone more knowledgeable to suggest which of these might break compatibility.

EDIT: Well, I got bored again, and started building my own EXEs. 6140 Does not break the launcher. 6146 crashes the launcher the same as any more recent nightly. 6144 and 6145 I was unable to build using MVSC_2010 express; got a whole host of error messages I haven't yet bothered to copy down.

[Iss Mneur]

Thank you for your digging into it.

Crap 6144 is the sound code build.  It is also the only one in that range that could affect the launcher. Don't worry about not being able to build the those two.

Please try the attached build.

EDIT: Oops wrong build.

[Alan Bolte]

A non-inferno build, eh? Doesn't crash the launcher, runs fine.

[Iss Mneur]

Oops.  I thought we had already changed the build profiles in trunk to make inferno the default (but of course I never checked either ).

Not that it should make any difference, here is the same build, but as inferno and SSE2.

[attachment deleted by a basterd]

[Alan Bolte]

Actually, it does make a difference. The INF_SSE2 version crashes the launcher. I guess that narrows things down somehow?

Are you sure that's the same build? 'cause I tried building plain 3_6_13d using the current SVN (8048), and that still crashes the launcher.

[Iss Mneur]

Actually, it does make a difference. The INF_SSE2 version crashes the launcher. I guess that narrows things down somehow?

Are you sure that's the same build? 'cause I tried building plain 3_6_13d using the current SVN (8048), and that still crashes the launcher.

Interesting. I guess its time to break out the hex editor and figure out what is going on.  Can I get you to run the build that crashes the launcher and a build that doesn't crash the launcher from a console with only the -get_flags.  Please save the flags.lch that is generated by each build and attach them both.

I will have to verify when I get home, but this is the only code change that I have made since sometime last week so the second build should have built with the same code, just different compiler options.  The first build that I had you try is changed from the current trunk so that crash isn't really a supprise.  The second build that I posted has the same change as the first build, just built with different options.

[Alan Bolte]

Attached.

[attachment deleted by a basterd]

[Iss Mneur]

Okay, fs2_open_3_6_13d_INF_SSE2_Iss_Mneur_flags.lch was not generated by the binary that I attached above.

Have you tried running the launcher as administrator, selecting one of the problematic executables, then restarting the launcher normally and try selecting one of the crash causing executables?

[Alan Bolte]

Whoops! I must have renamed the wrong .exe somehow. I downloaded the .exe again and generated a new flags file, though I dunno if you'll need it since your download doesn't actually cause a crash.

Sorry about the wasted time.

Have you tried running the launcher as administrator, selecting one of the problematic executables, then restarting the launcher normally and try selecting one of the crash causing executables?

If I hadn't before, I have now. Crashed as administrator, crashed again without administrator. In a separate test I tried XP compatibility mode - no change. Also no change running Windows XP Mode (Windows Virtual PC).

[attachment deleted by a basterd]