Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Test Builds => Topic started by: WMCoolmon on February 18, 2008, 04:31:48 pm
-
http://fs2source.warpcore.org/exes/latest/C02182008.zip (7.76MB)
Includes Murleen's widescreen fix. Based on my last stable scripting build.
-
Awesome! thanks allot its nice to see freespace in my MacBookPro's native resolution. Btw, is taylor's sdr1119.vp suppose to work with this? As I'm getting nothing with it.
-
you can enjoy the game also using MacOS X -> see my signature ;)
-
Thanks, but I sort of given up on the MacOSX version, though I'm sure Taylor has fixed the shader bugs by now. For one thing, I can actually set antialiasing. Besides I prefer to have all my games run on windows and leave my work stuff on the MacOSX. That way, when I'm working, I'm not tempted to go click on a game Icon. :D
-
To be honest, I also use BootCamp from time to time for a game - or PCS2.0.x or FRED or for 3.6.10 builds :nervous:
-
This is beautiful to behold. Actual 16:9 and 8:5 (16:10) res support!
Too bad it's so chunky that it is nigh on unplayable. Suppose that pointing it at the 3.6.10 Beta's w/ Normals (that it doesn't support) doesn't help any.
Massive Battle: 10-14 FPS at begining, with improvements: once all the shivans are dead up to 24 FPS.
1207 and 0217 XT's: 34-40 FPS and up to 60 once 2 Shivans are dead.
(Note: Shivans means Cap Ships. Doesn't matter which ones.)
-
very nice indeed. the video stutters every 5-7 seconds on my x2 4600+ and 7900gt. If I set affinity to just one core it chunks like Zacam said. Overall, very impressed with this build. Keep up the good work!
-
This build shouldn't have GLSL, so normal maps won't do anything with it. They won't be loaded or affect gameplay whatsoever. Unless WMC somehow snagged a copy of Taylor's code.
-
Excellent. I got that main menu script working now, and ts.isCurrentPlayerMulti() seems to be working as I expected it to. Thanks a bunch! Now as soon as I get my old files back I should be able to tie together some sort of testing pack for the devs.
-
this works nice on the laptop.
no moving suns and accurate lead indicators!
-
this really needs to be rolled into Taylors XT builds ;7
-
this really needs to be rolled into Taylors XT builds ;7
It was ... 4 releases ago. :)
-
Hehe...yup, on 2/15 it seems.
-
Pardon my ignorance, but where could I find these new XT series builds with widescreen fix enabled? I can't seem to find them from either browsing the warpcore directories, and obviously they don't seem to be on the Recent Builds forum open for download either.
Are they some kind of dev-exclusive material? :nervous:
EDIT: Yay, thanks. :)
-
Try here (http://icculus.org/~taylor/fso/willrobinson/Xt0222-win32.rar).
-
no Xt0222-osx.tgz :(
-
Nope, last one I know of is 12/08, but you might check the cross platform development threads for any other interesting stuff. Although it seems you've already posted your own there. I don't know what source you based that build off of, but you might try getting a copy of taylor's code updates and integrating it if you can't wait. He also modified Murleen's patch a bit, might want to check on that too.
-
my build is based on the fs2_open 3.6.9 source tarball posted by taylor http://www.hard-light.net/forums/index.php/topic,44374.0.html (http://www.hard-light.net/forums/index.php/topic,44374.0.html)
I got the latest source from svn, but taylor is working on it and it does not compile under MacOS X/XCode yet, but I am patient :)
-
does this fix fov?
-
It includes the fix that Murleen posted about fixing FOV on widescreen and other non-standard resolutions. Might even help when using non-standard FOVs on normal resolutions, haven't tested it yet.
-
Check out Mantis Issue 0001617 (http://scp.indiegames.us/mantis/view.php?id=1617).
Seems so far to only affect builds with this fix, but the cause may or may not be related to the fix.
-
Another possibility is a side effect from the scripting system. WMC committed that before the 15th, and Taylor probably updated his base before making his newer builds. So there's any number of places it could have come from. I would love to hear how the widescreen patch could have caused this though, if that's the case.
-
If the scripting system has been committed to the stable branch, it wasn't me that did it. I just released a build. I did commit some miscellaneous code bits, but most of those involved graphics or parsing and were essentially isolated.
-
Oh I thought you commited it, my mistake. Then yeah, it would have to be murleen's fix or something else that was commited between December and February probably, since not many builds were released over that timespan.
-
Murleen's fix doesn't even remotely touch anything resembling the physics code, which is pretty much the only place a glide related problem could be located.
About the only change related to the problem was rev. 4381 (http://svn.icculus.org/fs2open?view=rev&revision=4381), which was a commit of various code on 12/28. And I mention that rev in particular since the bulk of that commit was glide related changes and it was the last set of glide related changes that I'm aware of.
-
Right, that was me, and that's the revision that did it.
Half of that is intended (sort of), but the match speed thing needs a fix. Working on it.
-
Yeah I didn't think it would have been Murleen's fix, but I hadn't heard much about any other commits in the last few months, although I was sure there had been some.