Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Test Builds => Topic started by: WMCoolmon on April 28, 2004, 10:52:46 pm
-
Fred 2! (http://fs2source.warpcore.org/exes/latest/fred2_open_c04282004.zip)
I finally got the Hull and Subsys repair cap boxes added. They're in the Mission Specs dialog. This means when a support ship docks, it will only repair up to that % and then stop. If the % is already higher than the cap, it won't repair at all.
Note that these are floating point numbers, so if you're feeling particularly nasty you can set it to 99.9% (or .000001%, whichever floats your boat). :D
-
hey this thing doesn't slice!! i want a ****ing refund
we need to get you access to post in the recent builds forum as well
-
Does this build support Kazan's -htl, -mod, and other flags? Does this fix some of those LOD switching settings?
-
It should support all that stuff, but it doesn't fix any bugs.
phreak: to slice, add a slash beam onto a ship and select "Beam-free-all" in the mission specs dialog. ;)
-
nice, thanks.
one question though, can the SCP guys please set a conform dating scheme, we've got yyyymmdd (Taylor, me for personal builds)
mmddyyyy (you), mm-dd-yyyy (Goober), mm-dd-yy (Bob, IIRC) and ddmmyyyy (i forgot). And then some variations on this theme.
-
Bah to floating points. Can't you make them integers?
-
Found... well... -something- wrong. A mission I have which works fine with the 20-03-2004 fred build, and works fine in-game, locks this fred version up within 2 seconds of loading it, forcing me to kill the process from the task manager. That's with HTL disabled and no table warnings on startup, so that's not the problem.
Trying to disect the mission bit by bit now to see what's causing it, but in the meantime is there any chance you could post a debug build of this? Might help me find out what's wrong if it actually tells me something instead of just locking up.
-
WMCoolmon, did you fix the htl flag on this?
-
It's still reversed. Easy way to tell is that ship outlines only work when it's off (for me anyway ;))
-
You mean it wasn't fixed? :wtf:
It only seems to involve removing two exclamation marks, though this "nohtl" variable setup is somewhat odd.
Fixed? (http://fs2source.warpcore.org/exes/latest/fred2_open_c04282004.zip)
-
Still locks up, HTL flag still reversed (need to use the -fredhtl command line to turn it off, instead of to turn it on). One symptom I noticed before the lockups in the new build was some weird vertical lines from the grid plane up into nothingness.
20-03-2004 Fred build:
(http://swooh.com/peon/mtbjarkow/Pics/Fred.JPG)
28-04-2004 Fred build:
(http://swooh.com/peon/mtbjarkow/Pics/BuggedFred.JPG)
Sorry for blotting out so much, but hey, it's only the lines that are important, and besides not doing it would spoil the fun of playing it :D
-
:doubt: I'll look into it tomorrow.
*Wonders why Kazan never fixed this*
-
Here's another example of the same thing.
These are from the mission from the Great War when you have to disable the HoL cruiser Ramses.
(http://www3.sympatico.ca/daniel.topps/FREDOGL-Screen4.jpg)
Notice how the vertial elevation and declination lines are not attached to any object and they are also only originating from the exact page center. Also notice how the waypoints are way (no pun intended) out of position. Now see what happens (or doesn't happen) when the camera position is panned up slightly:
(http://www3.sympatico.ca/daniel.topps/FREDOGL-Screen5.jpg)
The lines will remain at these exact positions on the screen, until the objects they are attached to move out of the camera view, at which point the vanish.
I first noticed this in Kazan's build with -mod support, but didn't make extensive use of the build to notice how annoying it was. When I was asking him what he had done with the LOD switching ranges, he said that he hadn't done anything, which means it had been introduced into the FRED code, but no public build out had included the change until that point. My guess is that the same is true here. As such, Random Tiger is probably the man to talk to on this problem.
Hope this helps.
Later!
-
Originally posted by WMCoolmon
:doubt: I'll look into it tomorrow.
*Wonders why Kazan never fixed this*
If I remember correctly the lines thing is actually an OpenGL bug that was present in CVS before Kazan made the -mod build.
-
I was referring to the -htl flag being reversed, actually.
-
Originally posted by karajorma
If I remember correctly the lines thing is actually an OpenGL bug
I've got fix, well pretty much a wierd hack actually, in CVS that should get lines working in OGL when in HTL mode. Non-HTL should work fine just as before.
Lines didn't work right when the projection matrix was set so I disable it in those special cases, draw the line, then turn the projection matrix back on. It was the only thing I could come up with that worked and didn't kill the framerate.
-
thats since the lines are already translated into 2d. it probably wouldn't be that bad of an idea to change it.
-
The out of place vertical lines occur both in HTL and non-HTL.
-
Good: No complaining about weapons.tbl at the beginning.
Bad: FRED2 doesn't save the recent files list (could this be because the older FRED2 Open is still there?)
Ugly: When I close FRED2 it gives me an unable to swap buffers error. (Something to do with opengl, which my crappy onboard gfx card doesn't support. But it didn't happen with previous versions and easily ignorable)
Other than that, its pretty good. :)
-
it's not your crappy onboard video, I've got a ATI 9800 Pro and I get the same error plus the vertical line problem
-
there's some special compile flag to set that prevents the swap buffer error from occuring, perhaps i should change it to a runtime variable (im sure there's a Fred_running var floating around the codebase)
-
Any chance a Fred button can be put on the luncher?
-
Originally posted by ubermetroid
Any chance a Fred button can be put on the luncher?
That's not a bad idea but it's probably a lot of work for something which we can do with 2 minutes worth of playing with shortcuts :)
-
can this work with Inferno?
-
What does Inferno need to work? Or you can just dl and try it.
-
you need to define INF_BUILD for inferno to work
in Visual C, i create a different configuration for the projects that have INF_BUILD defined. it the filename and the intermediate file locations will also be changed, so if i need to build a standard release and an inferno release, i can just change it using the drop box.
-
Well, I can't build an Inferno version of this right now because I clean updated my source files so the .NET compiler is unhappy.
Newest version (http://fs2source.warpcore.org/exes/latest/fred2_openC05022004.zip)
One fix (drumroll please)...
...The HTL flag finally works right! :D
-
It's great to see that the hull repair cap values are now supported. The htl should be defaulted to off though, as it makes the editor completely screw up. It won't load up most of the missions I have, giving an illegal operation error just as it starts to display the ships. This occurs with all my PI ones and all but one or two of the main campaign missions, and those that do work show the ships in the wrong places. Everything works okay when I turn off htl.
I get the lines thing that people talked about (without htl, haven't been able to test it with) but things work fine otherwise.
Does this version support the usual ship outlines mode by the way? It of course does not look as good but it makes ships much easier to spot, especially on a background, which can be useful in the editor.
Found... well... -something- wrong. A mission I have which works fine with the 20-03-2004 fred build, and works fine in-game, locks this fred version up within 2 seconds of loading it, forcing me to kill the process from the task manager. That's with HTL disabled and no table warnings on startup, so that's not the problem.
It probably has nothing to do with your mission; it happens on almost every mission I try it on and only when it tries to display the stuff after loading it.
-
Originally posted by Exarch
Found... well... -something- wrong. A mission I have which works fine with the 20-03-2004 fred build, and works fine in-game, locks this fred version up within 2 seconds of loading it, forcing me to kill the process from the task manager. That's with HTL disabled and no table warnings on startup, so that's not the problem.
Trying to disect the mission bit by bit now to see what's causing it, but in the meantime is there any chance you could post a debug build of this? Might help me find out what's wrong if it actually tells me something instead of just locking up.
:o Sorry, I missed your post. Only noticed when CP quoted it. I'd have to do a rollback such to get the code working again w/ my compiler, so it'll have to wait until after the post-3.6 feature rush.
-
Agh, stupid FRED. :mad: When trying to save a mission I get this error.
Error: Failed attempting to reload mission after saving. Report this bug now!
File:.\FREDDoc.cpp
Line: 509
---Call Stack Junk---
And now FRED won't load it at all. I tried an older version of FRED and it still doesn't work. To make matters worse, FRED won't open any of the backups, and the most recent ones are just the template when you first open FRED.
Strange thing is it only affects one mission, all the rest work fine.
-
Originally posted by WMCoolmon
Note that these are floating point numbers, so if you're feeling particularly nasty you can set it to 99.9% (or .000001%, whichever floats your boat). :D
Originally posted by Goober5000
Bah to floating points. Can't you make them integers?
?