Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Test Builds => Topic started by: taylor on February 28, 2010, 06:38:11 pm
-
Test build for new Launcher: http://icculus.org/~taylor/fso/testing/Launcher.7z
Changelog:
- Support for new-sound builds
- Fix various memory errors
- Handle command lines dynamically (Mantis #2068)
- Fix ini file saving (Mantis #1920)
- Better resolution support (Mantis #1958)
Please report any issues, old or new.
-
About mantis:1920:
Now when I have some mod selected, hit "no mod", select another binary and hit Cancel I have no mod selected after launcher restart which is not good as well.
-
When you select another binary the settings are automatically saved. So cancelling at that point doesn't make any difference. This is no different from how it worked before, it just has the bug fixed now.
-
I'm awfully late in posting this, but apparently old launcher doesn't actually apply all flags it says it did. On the first run this new beta launcher displayed some flags were turned off. Probably another issue with the old launcher and long command lines.
-
Question: Has anything been done towards making the AA slider work correctly?
-
Yep. Hery had fixed it, but he went AWOL due to RL issues and has not submitted a .patch to date.
-
The Launcher doesn't like hyphens, there is a fix out there for this already, Goober said he'd shoot you an email~
-
Launcher just refuses to run on my end (I'll double click it, and then it'll die), after a period of working fine. Not sure exactly what caused it, don't have any ideas at the moment.
-
The Launcher doesn't like hyphens, there is a fix out there for this already, Goober said he'd shoot you an email~
This seems to be the case indeed. I created a mod.ini that includes fsport-mediavps in its secondarylist. Launcher 5.5f throws an error "Invalid mod.ini multiple mod parameter; only -mod calls are allowed", but 5.5e works.
-
I heard the hyphens bug has been fixed at least. So can we please have a new launcher build, thank you very much.
-
I don't have the ability to build one for a while, but the code is all in SVN now so somebody else should be able to get a new one out.
-
On it. It still only builds with VC6?
-
Doesn't build with VS2010, I know that much.
-
Good thing I still have VC6 on my VM then.
Actually I just got it compiling in VS2010 on my machine. Running is another story though.
-
Launcher 5.5f Beta 2 (http://swc.fs2downloads.com/files/Launcher_55f-beta2.7z)
Give this a spin guys.
Taylor, I can't commit to the Launcher_5_5 branch, although I'm not sure we want to try to commit my changes to trunk first since there's already development there and I'd likely be missing files from the project file.
If this works we'll just rename it to 55f, it's not in the file properties as beta anymore but in case it's broke I don't want it getting widespread without some differentiation.
-
"The program can't start because MSVCR100.dll is missing from your computer."
-
Bah it's shared DLL not statically linked. Not sure what to do about this.
For now I replaced it with a VC6 build.
-
still crashes the moment I select taylor's sound build
-
Not getting that with any of the launchers. What OS?
-
still crashes the moment I select taylor's sound build
Not getting that with any of the launchers. What OS?
Same here.
@Spoon: What FSO binary did you use before this one? What is the contents of your data/cmdline_fso.cfg file?
-
Taylor, I can't commit to the Launcher_5_5 branch, although I'm not sure we want to try to commit my changes to trunk first since there's already development there and I'd likely be missing files from the project file.
Sorry about that; it should have the correct permissions now.
If you mean the Launcher in trunk, then yeah, I don't really know what to do about that one yet. It still won't build as far as I know, and even if it does there is still too much missing from it to actually work properly. I don't really feel comfortable porting my changes there until I can actually test them to see if it all actually works. I assume that you are in the same position. I think that we should probably just keep with the 5_5 stable branch for now, and then port anything back to trunk if that time comes (ie. if we haven't officially dropped it for wxLauncher).
@Spoon: What FSO binary did you use before this one? What is the contents of your data/cmdline_fso.cfg file?
Also, make sure that you have an up-to-date OpenAL installed, or just re-install it. The new stuff requires working enumeration support and I seem to remember there being an issue with that in certain older OpenAL versions. Although, I can't actually recall whether what OS that was for, so it may be something else entirely. I do know for certain that there was a strange crash bug on Windows with certain OpenAL versions when I originally started playing around with better initialization code in the old Xt builds however.
-
Also, make sure that you have an up-to-date OpenAL installed, or just re-install it. The new stuff requires working enumeration support and I seem to remember there being an issue with that in certain older OpenAL versions. Although, I can't actually recall whether what OS that was for, so it may be something else entirely. I do know for certain that there was a strange crash bug on Windows with certain OpenAL versions when I originally started playing around with better initialization code in the old Xt builds however.
This seemed to be the cause. I never updated OpenAL after I installed FSO (which was at the start of 2009, according to the download page the most recent version was released in the summer of 2009). Works now.
Well, the more you know.
-
Under this launcher (maybe even the one before it), there is an option under Troubleshooting that is "Fix color issues on some ATI cards".
What does this do/fix, and what cards require this?
-
Let me put it this way: If everything in the mainhall is coloured correctly, you don't need it. IIRC, No cards currently on the market need it.
-
It's been in there forever. Additionally, the missing commits from this launcher revision were added, and a new build was made with VC6. It's linked in the RC3 release thread.
-
Yep. That's the one I grabbed. Working nicely, though AA/AF sliders are still broken. I'm assuming Hery's fix never found its way here :P
-
Nope, he disappeared apparently without leaving that behind.
-
Man, I really hope that guy comes back. His work with post-processing was great.
-
Actually, his work with post-processing was atrocious. His implementation was very poorly organized and contained lots of bugs. Fortunately, it was also very poorly integrated, so we turned it into an experimental feature if it promised not to step on the rest of the code. :)
-
Well, the bloom looks decent to me, so I don't care much for what it looks like under the hood :)
-
Yes, well, it's our job as SCP to care how it looks like. Because we're the ones who have to deal with it when it breaks and someone, inevitably, complains.
-
Actually, his work with post-processing was atrocious. His implementation was very poorly organized and contained lots of bugs. Fortunately, it was also very poorly integrated, so we turned it into an experimental feature if it promised not to step on the rest of the code. :)
Why weren't these comments made during Antipodes #4?
If it is an experimental feature again, and especially if it is not being actively worked on, it should be moved back to Antipodes.
-
Why weren't these comments made during Antipodes #4?
Probably because very few coders take the time to review other coders' code.
If it is an experimental feature again, and especially if it is not being actively worked on, it should be moved back to Antipodes.
I would concur with this. Hery seems to have disappeared and I don't know when/if he'll be back.