Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Test Builds => Topic started by: taylor on December 27, 2006, 03:26:56 am
-
Here it is, the last build before 3.6.9 final, so be sure and test it well... and quickly. :)
Build for:
Windows (http://fs2source.warpcore.org/exes/3.6.9-RC8.rar)
And:
Source Tarball (http://fs2source.warpcore.org/exes/linux/fs2_open-3.6.9-RC8.tar.bz2)
And don't forget these if you haven't already gotten them:
http://fs2source.warpcore.org/mediavp/mp-710_adveffects.rar
http://fs2source.warpcore.org/mediavp/mp-710_effects.rar
http://fs2source.warpcore.org/mediavp/mp-710_models.rar
-
:nervous:
I'm sorry, but I have already a problem: when I go in the mission simulator, the game starts switching between the mission simulator screen and the tech room screen. I've tried pressing "Esc", "Enter"... The only thing I can do to resolve the situation is open the Task Manager and shut down the game manually. It does that with every mod.
I'd have reported this in Mantis, but for some strange reasons my Mantis account has been removed.
-
I'm sorry, but I have already a problem: when I go in the mission simulator, the game starts switching between the mission simulator screen and the tech room screen. I've tried pressing "Esc", "Enter"... The only thing I can do to resolve the situation is open the Task Manager and shut down the game manually. It does that with every mod.
Huh? You mean when the simroom popup comes up when the missions are being read? Are you using D3D or OGL, fullscreen/windowed?
-
I'm using OpenGL with fullscreen.
-
But it's that popup, correct? It should only last a few seconds so you shouldn't ever have to break out of it.
Flipping between the old and current screen as a background is an old bug though, and I haven't been able to fix it 100% (works in windowed but not fullscreen, on ATI but NVIDIA, in Linux but not Windows, and every option in between). It's purely cosmetic though, and probably already in Mantis.
-
But it's that popup, correct? It should only last a few seconds so you shouldn't ever have to break out of it.
Flipping between the old and current screen as a background is an old bug though, and I haven't been able to fix it 100% (works in windowed but not fullscreen, on ATI but NVIDIA, in Linux but not Windows, and every option in between). It's purely cosmetic though, and probably already in Mantis.
No, it's not that problem. It's difficult to describe by words. I tried to capture a video of it to show what happens, and the situation became extremely strange: while I was capturing the video, everything worked fine :mad:, so I minimized FS2 to deactivate FRAPS. When I reopened FS2, it continued switching between minimized and mission simulator screen. Also this time, I could only open the Task Manager to shut down FS2.
The original problem was: I selected the Mission Simulator in the tech room, and instead of seeing the "Reading mission XXX.fs2" (or whatever it is) pop-up, I saw briefly an empty mission list, then it switched back to the tech room and then back again to an empty mission list (it is so quickly that it does that about 10 times per second). It continued doing so until I shut down the game.
That was the better I could explain. I hope you understood. :)
-
The original problem was: I selected the Mission Simulator in the tech room, and instead of seeing the "Reading mission XXX.fs2" (or whatever it is) pop-up, I saw briefly an empty mission list, then it switched back to the tech room and then back again to an empty mission list (it is so quickly that it does that about 10 times per second). It continued doing so until I shut down the game.
Yeah, that's the same problem that I'm thinking of, but the popup should be visible over the mission list while it's reading missions. It also shouldn't force you to kill the game to get out of it, since the popup will go away after a few seconds. Either way, I can't get it to mess up like that, and none of that menu code has changed since RC6 as far as I know.
Get rid of everything except for the retail VPs, and make sure that you don't have any missions in data/missions/, and try again. It may actually be some bad data which is causing it (freaky as that may be, it is possible).
Unless someone else reports this same problem though, a serious look into the issue will have to wait until after 3.6.9 is released.
-
Get rid of everything except for the retail VPs, and make sure that you don't have any missions in data/missions/, and try again. It may actually be some bad data which is causing it (freaky as that may be, it is possible).
Neither doing this helps. :(
I'll continue to use 3.6.9 RC7.9X until the release of the official 3.6.9. Anyway, thank you!
-
Hi,
I have a problem with SCP and the Freespace2 campaign.
I have installed the newest RC (RC8) with all VPs and FS1-port.
I've played the FS1-campaign and Silent Threat without any problems, but then I wanted to play the FS2-campaign I'm getting errors.
I tried it with a new pilot, but after the 3 training lessons I'm getting always 4 errors.
I've attached screenshots of them.
btw: I had these problems also with the RC7.9x. Also I tried the Launcher with and without any features.
[attachment deleted by admin]
-
You didn't happen to install the port to your main FS2 directory instead of using a mod directory, did you? Those errors look suspiciously like and out-of-place table from some mod or other. At least if it's that, it's an easy fix - Just move it to a mod directory instead :)
-
Ok, I think that was the problem. I should have removed the fs1-port earlier by myself... ::)
Not it works!
Thank you!
-
You probably didn't need to remove the port. Was the port in it's own folder or slapped down in the main Freespace2 folder? Cause if it was the first one all you had to do was go into the launcher and change your selected mod to mediavps.
-
I'll continue to use 3.6.9 RC7.9X until the release of the official 3.6.9.
Well, keep in mind that RC8 will probably be identical to the official 3.6.9...
-
alt+tabbing back into the game under OGL on an WinXP rig with Radeon x800 causes garbled images ingame until I do esc+enter, then the screen is ok again. Under interface I need to just hit enter a few times to get to the next interface screen, if I don't, the screen stays totally black.
-
alt+tabbing back into the game under OGL on an WinXP rig with Radeon x800 causes garbled images ingame until I do esc+enter, then the screen is ok again. Under interface I need to just hit enter a few times to get to the next interface screen, if I don't, the screen stays totally black.
Don't ALT-TAB, it's known to not work very well. It will be made better for 3.7, but for now you are pretty much on you own if you try it. :)
-
It would be nice for the official builds to be compiled with full voice synthesis and voice recognition support.
-
Ok, fair enough, just thought I'd report everything I spotted. The rest of the stuff seems to be working fine, though.
-
I have it.
The campaign list still has that bug...
I'm not having problems like DySkO, but I want to use the new build of FRED. Can I use RC8 FRED Open with the RC7 build?
Is there an ETA for the release of 3.7? As you know we are interested on the unlimited Species tbl...
neoterran:what do you mean? This build has the voice implemented...
I have opened FRED RC8. The ships names font colour is different...now it's dark.
I placed a Mjolnir a few dozen metres away from the player, and both the camera coords and the coords of the Mjolnir displayed near its name became white and not readable. Though now it's ok, I want to know if this problem is serious or not.
-
alt+tabbing back into the game under OGL on an WinXP rig with Radeon x800 causes garbled images ingame until I do esc+enter, then the screen is ok again. Under interface I need to just hit enter a few times to get to the next interface screen, if I don't, the screen stays totally black.
Don't ALT-TAB, it's known to not work very well. It will be made better for 3.7, but for now you are pretty much on you own if you try it. :)
It actually seems to have gotten worse over time, although it may have more to do with changing video card drivers than anything else. I used to do it all the time on an old 6800GT a little over a year ago, the 7800s couldn't do it at all (instant BSOD) and on an X1900, it works about half of the time and does what kasperl described at other times.
-
Which drivers are you using? I was using the Omega drivers, but was getting ATIogl crashes. I just switched to the Ngo drivers. They are current, and come with advanced tray tools which expose some amazing features I've never seen before. I'm not crashing anymore, but my fingers are crossed.
-
Somehow the build managed to affect desktop gamma settings, everything changed to a darker tone after playing the game... if I remember right, I changed the gamma slightly in F2, then quit with Shift+Esc and I don't know why or how, but the gamma setting stayed behind. The colours reverted back to normal after restarting the machine...
I'm on my parents' PC, which has an ATi Radeon 9200 SE with original drivers [sic, don't blame me on that], Windows XP SP2, AMD64 3000+ XP, 512 MB DDR-SDRAM. Was using the MediaVP 3.6.8 zeta without Advanced effects... Even withhout them, this poor thing can only run the game at 30 fps max, facing empty space. :rolleyes:
-
Somehow the build managed to affect desktop gamma settings, everything changed to a darker tone after playing the game... if I remember right, I changed the gamma slightly in F2, then quit with Shift+Esc and I don't know why or how, but the gamma setting stayed behind. The colours reverted back to normal after restarting the machine...
I'm on my parents' PC, which has an ATi Radeon 9200 SE with original drivers [sic, don't blame me on that], Windows XP SP2, AMD64 3000+ XP, 512 MB DDR-SDRAM. Was using the MediaVP 3.6.8 zeta without Advanced effects... Even withhout them, this poor thing can only run the game at 30 fps max, facing empty space. :rolleyes:
I had a similar problem also with the previous build: if I didn't shut down the game correctly, everything was brighter. I resolved the problem re-running FS2 and re-closing it.
I know, it's a stupid method... :nervous:
-
Which drivers are you using? I was using the Omega drivers, but was getting ATIogl crashes. I just switched to the Ngo drivers. They are current, and come with advanced tray tools which expose some amazing features I've never seen before. I'm not crashing anymore, but my fingers are crossed.
I am using 6.12 without the CCC. I don't get any actual crashes when alt-tabbing, but I have to open a new interface window blindly in order to make things show up again, and there is often a long delay before it gets back into the game. It takes less time and effort to just exit out of the game and get back in instead of going through that. :p
I had a similar problem also with the previous build: if I didn't shut down the game correctly, everything was brighter. I resolved the problem re-running FS2 and re-closing it.
I used to do exactly the same thing. :D
This build doesn't have the brightness bug on my end though.
-
I have it.
The campaign list still has that bug...
The screen flip thing, or the have-to-kill-it-to-get-out thing? The screen flip thing will just have to wait. The only time that I've actually had it fixed a bunch of ATI users reported that they would only get a single color instead of a background, so I had to break it again for them.
Is there an ETA for the release of 3.7? As you know we are interested on the unlimited Species tbl...
"Many years from now...", as a best guess. ;)
There is an awful lot of new features slated for 3.7, and a tremendous amount of code is going to get added, removed, or completely rewritten. It will be ready when it's ready, but it's far too early to give any sort of real guess as to when that might be.
I have opened FRED RC8. The ships names font colour is different...now it's dark.
I placed a Mjolnir a few dozen metres away from the player, and both the camera coords and the coords of the Mjolnir displayed near its name became white and not readable. Though now it's ok, I want to know if this problem is serious or not.
Hmm, might be related to the secondary color fix I had made. I double check on that, it would be an easy thing to fix if that was the cause.
Somehow the build managed to affect desktop gamma settings, everything changed to a darker tone after playing the game... if I remember right, I changed the gamma slightly in F2, then quit with Shift+Esc and I don't know why or how, but the gamma setting stayed behind. The colours reverted back to normal after restarting the machine...
The game does have to exit properly in order to be able to reset the gamma. As Darth DySkO mentioned, you should be able to fix it just by running the game again and then exiting. Another option is to juse run with the -no_set_gamma option to disable gamma setting at all. Perhaps not the best option if you actually need to use the gamma setting, but it should beat having to restart your machine when the gamma doesn't get reset properly.
-
Sorry if this is the wrong place, but in the mission after Bearbaiting, High Noon, sometimes I don't receive orders to jump out. This happened in the previous build as well.
-
Sorry if this is the wrong place, but in the mission after Bearbaiting, High Noon, sometimes I don't receive orders to jump out. This happened in the previous build as well.
That's not related to the build I don't think... did you try destroying both wings of Basilisks?
-
That's not related to the build I don't think... did you try destroying both wings of Basilisks?
Ahh, that could be it, I was concentrating on killing the big ship, not the fighters, but all my objectives were completed anyway.
-
Do you get the following message?
"Well done, secure the area and our work here will finished."
If so are you sure you've wiped out all of Cancer wing?
-
I am having issues with rc8. whenever i start a mission, the game keeps pausing on me. everytime i press escape the game immediately pauses again. if i alt tab to finder and then go back to freespace, it seems to fix the issue and i can unpause the game, but i don't know why. this happened with rc7 too, but alt tabbing out didn't fix it in that build.
-
:nervous:
Please, don't kill me:
I don't know why, but now RC8 seems to work perfectly :wtf:
-
bar a few table errors in debug mode, and a strange crash in weapon config screen that i've been unable to replicate, this RC is a winner.
-
Tried out the debug on OGL fullscreen using a mod with missing textures (on purpose, I don't use nameplates and I don't know how to make blanks to cover them up :P).
1024x768 for the game, 1280x1024 for desktop. Chose a ship with the missing texture and I get sent to the desktop. I clear the error and try to go back in, but I end up seeing Windows in the game resolution. ALT-TAB a few times and I get back in, but everything just jerks. One jerk, the ship (in Techroom) is facing you, on the next jerk after roughly 2-3 seconds, it's facing left and so on.
I do feel that somewhere along the line (not just this build), Alt-Tab got worse, but I don't think it's a driver problem because I didn't see any changes caused by drivers to my PCI 5700LE for a long while now (new drivers work on my old card, but the changes now affect only the newer cards e.g. 6-series and above). Unless they added something without documenting... :blah:
Otherwise the build is all good and dandy on my end.
-
debug build causes a CTD right after mission is loaded.
[attachment deleted by admin]
-
With no errors?
-
Another strange thing happened with FRED Open:
Yesterday I could move a chosen ship with the numpad and A,Z,-,+ ecc. today I move and rotate only the camera,as usual.
-
Do you get the following message?
"Well done, secure the area and our work here will finished."
If so are you sure you've wiped out all of Cancer wing?
I THINK I heard the "Well done" message, and Cancer wing was destroyed.
Someone should probably move this since it's OT.
BTW, I did find a small thing the other day, the mission was Exodus, and in the briefing there is a line that is read twice, the one that goes "We need to deploy your..."
-
debug build causes a CTD right after mission is loaded.
Which mission?
The CTD is actually an Int3(), but without the fs2_open.log it's impossible to tell where it came from. I get these quite a bit in Prologue though, due to sexp issues (which are mostly just hitting on code which isn't properly updated to handle what you guys are doing), but there isn't anything we can do about that until after 3.6.9 since it would require an extra month or two of build testing before we're sure no AI was broken.
-
Another strange thing happened with FRED Open:
Yesterday I could move a chosen ship with the numpad and A,Z,-,+ ecc. today I move and rotate only the camera,as usual.
You probably pressed the "T" key by accident.
-
debug build causes a CTD right after mission is loaded.
Which mission?
The CTD is actually an Int3(), but without the fs2_open.log it's impossible to tell where it came from. I get these quite a bit in Prologue though, due to sexp issues (which are mostly just hitting on code which isn't properly updated to handle what you guys are doing), but there isn't anything we can do about that until after 3.6.9 since it would require an extra month or two of build testing before we're sure no AI was broken.
Can't tell for sure now. I believe the 5th mission. But: older debug builds (hoopla for instance) work.
-
You probably pressed the "T" key by accident.
Yeah. I have completely ignored that function...until now.
-
Has anyone who gets the placement issue in the Derelict mission "Rites of Passage" tried this new build yet?
Taylor, when I get back to my PC in a week or so I'll test out this build and see if it duplicates that crash issue I reported in Mantis. If so, I'll send you all the log files for the new build (and if not, I'll get the other log to you as soon as possbile).
Is this just a compilation of fixes since RC7.9, or is there a list of new corrections made for this build?
-
Ok, I've delurked and found that INFA was finally released, yay. Time to reinstall FS2 and set it up to play. Went to get this, the latest concoction by the SCP people, and I'm already having a problem. It's probably (I hope) an obvious problem. I probably forgot to download something. Anyway, here's the issue.
I downloaded the build here, and I opened up the launcher. I selected fs2_open_3_6_9-RC8.exe and hit ok. Then I got this error message. "This application has failed to start because OpenAL32.dll was not found. Re-installing the application may fix this problem."
Is this just another reinstall FS2 issue? Though, that'd be strange as I just reinstalled it last night to be safe. Any help would be appreciated.
-
It quite literally tells you the cause. You need to install OpenAL (http://developer.creative.com/articles/article.asp?cat=1&sbcat=31&top=38&aid=46) :)
-
That'll do it. :P You SCP folk are always tossing new stuff at me whenever I delurk.
Thanks a ton for the help.
-
I think the fade sexps are broken in this version. I'm almost certain they were working fine in 7.9, but I'll need to double check it.
[edit] Yeah, it works fine in 7.9. I have made a mantis entry on this.
-
@Taylor : I'm getting reports that the game (WCS) hangs when the movies are being played, I encountered that myself, though not everytime.
Any idea what could causing this ?
-
@Taylor : I'm getting reports that the game (WCS) hangs when the movies are being played, I encountered that myself, though not everytime.
Any idea what could causing this ?
Not really. It's only really been tested when using OpenGL though, so see if the people getting hangs are using D3D or not. I don't think that should actually make it hang, maybe just display weird, but it's something to consider I guess.
And I suppose that by "hang" it means that the movie doesn't play and that hitting SPACE, ENTER or ESC doesn't get out of the movie, correct? It could be something related to the timer in that case, and it would just sleep for a long time between frames and that would give the impression of it freezing up. I'm not really sure why that would happen though. I'm using the same timer code as is used for MVEs (with minor changes for frame time reporting differences) so it's a little strange if it is a timer/sleep problem since that base code has been in use for quite some time.