Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Test Builds => Topic started by: karajorma on October 28, 2007, 09:21:04 am
-
I had to put this up to see if it fixed a FRED problem Snail was having and I figured I might as well make a proper release of it anyway.
The build is based on CVS so it won't have any new code from the XT builds. It's an Inferno build so it will quite likely corrupt any non-inferno player file you run through it if you're not careful. It won't work in multiplayer either (only 3.7 branch Inferno builds work in multiplayer).
Only a couple of new things in here from me. The hits-left-single-subsystem I mentioned here (http://www.hard-light.net/forums/index.php/topic,50212.msg1015694.html#msg1015694).
Also included is the get-damaged-caused SEXP which returns the amount of damage any particular ship has done to any other one. Feel free to play with it but I won't guarantee that it will be in 3.6.10 unless this build gets some heavy testing (which is rather unlikely since I notice that Taylor put up an XT build a few minutes ago! :lol:
Anyway here's the build, FRED is included.
2007-10-29 Stable Branch - INFERNO (http://www.freespacefaq.com/Misc-Downloads/Builds/FSO-20071029-Inferno.7z)
-
Thanks. :)
-
On second thoughts I'm going to get rid of the hits-left-single-subsystem SEXP and just add another parameter to the existing SEXP.
For the life of me I can't understand why I decided to implement the fix that way. :rolleyes:
EDIT : uploaded the new build. hits-left-single-subsystem has been consigned to the dustbin of history! :D
-
Shame...I have just noticed it :blah:
Thanks :yes:
-
Are there any known issues with destroyed-or-departed delay in this build? I'm getting a strange problem, I'd like to know if it is somewhat connected to coding.
-
Same thing for messages sent from a string variable set as source...I save the mission and FRED crashes, corrupting the file... :blah:
-
There shouldn't be any changes to do with that in the build. Are you sure the source actually exists? Do you get an error in debug?
-
I circumvented both issues(destroyed-or-departed-delay and message coming from a string variable)with tricks.
There's something I can't circumvent: there's one mission that, apparently, shouldn't give problems. FRED doesn't report errors. I select the mission with the simulator. CB is ok, briefing is ok, I select commit...and after a few seconds FS Open crashes(the mission doesn't start, there still is the briefing interface during the crash). No errors are reported.
It's Sol1-09a, you should be able to get it in INFA internal(Woo's thread, 2-3 pages behind the last one).
-
Stick the bug in Mantis. Expecting SCP coders to fix a bug from a forum post is never a good idea. If something shiny distracts us between seeing the post and actually being in a position to code you're never going to see a fix.
-
I don't know how to use Mantis, the last time I tried it I got a bit nervous.
If you can get the mission you can do it yourself...
-
I can. I won't, but I can.
As far as I'm concerned if your bug doesn't bother you enough to learn to use Mantis it certainly doesn't bother me enough to worry about fixing it.
-
Ok, I'll do it.
I need to create an account...in the meantime, can you tell me if the mission is going to become public? It's important...
-
Same problem of the other attempt...where the hell is the confirmation e-mail? :wtf:
EDIT: I'll try with my mother's e-mail address...
EDIT2: Nothing...how do I activate my account?!? The confirmation e-mail(s) are nowhere to be found!
-
I gave up. I'm sending the file to shiv(he has a Mantis account).
I hope the mission won't be public... :nervous:
EDIT: :wtf: the file will be public! Oh God!
-
No need to put the actual file up. Just say where the mission is on the internal and at least 3 of the coders who might look at the problem should have access.
-
can't you make a bug report private? so only the reporter and the developers can see it?
-
I gave up. I'm sending the file to shiv(he has a Mantis account).
I hope the mission won't be public... :nervous:
EDIT: :wtf: the file will be public! Oh God!
:wtf: :wtf:
Well, if you post a mission in Mantis, yes, it technically goes public.
But unless you really make AN ADVERTISMENT like this stupid discussion, I really doubt that it's really going to become PUBLIC at all. (Nobody digs through Mantins looking for mod leaks...)
Just my thoughts...
-
Many of the Administrators also work as coders, so they should be able to get the mission from INFA internal.
-
can't you make a bug report private? so only the reporter and the developers can see it?
Yup.
Many of the Administrators also work as coders, so they should be able to get the mission from INFA internal.
"Two" is not "many".
-
Taylor should have access too (assuming access to Inferno gives you access to Inferno Alliance as well).
-
(assuming access to Inferno gives you access to Inferno Alliance as well)
It does not.
-
In that case we have to rock-paper-scissor between you and me I guess. :p
-
Or he could file a private bug report as was suggested. :p
-
?
I thought Administrators have access to all internal forums... :wtf:
-
Taylor's not a HLP admin, only GW.
-
Can someone please send him the mission(in case he doesn't have it)? Thanks.
-
Can someone please send him the mission(in case he doesn't have it)? Thanks.
File a private bug like we told you and stop demanding special treatment.