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 20, 2005, 06:40:53 pm
-
Cutscenes build features plus (http://www.hard-light.net/forums/index.php/topic,30702.0.html)
- Fixed crashing with new trails code, also added some optimizations
- Fixed briefing in nonstandard resolutions
- Fixed secondary lead indicator in nonstandard resolution
- Fixed objective completion text in nonstandard resolutions
- Fixed pause text in nonstandard resolutions
- Fixed time compression controls not working (broken in prev build)
- Prettified lightning arcs on damaged ships slightly
- Improved centered text in D3D nonstandard res
- Improved scanlines in nonstandard resolutions
- set-jumpnode-color
--node name
--R component
--G component
--B component
- Alpha component
--node name
--model
--show as normal model? (ie not wireframe)
--node name
--node name
-- Lock it? (False to unlock)
-- 0 for first-person, 1 for chase, 2 for external, 3 for top-down (optional)
- Added debug messages to techroom.
- New variables in mission file for jump node (see example)[/color]
Example:
$Jump Node: 1.0 3.0 4.0
+Jump Node Name: Dave's House o' Fighters ;;Technically a $ will work here too, it was the default, but a + fits in with the parsing scheme better, it is optional after all
;;New stuff
+Model File: FoD.pof ;;yes it works now
+Alphacolor: 255 0 255 255 ;;last variable is for alpha, ie transparency, 255 is full
+Hidden: YES ;;now you have to use show-jumpnode to make it show up[/color]
Notes:
lock-perspective will be force-perspective in future builds. I'd already compiled and zipped the builds when I realized I hadn't changed that.
Unresolved issues:
- Some people have reported crashes with regard to warping out
- FS2 seems to freeze up randomly on certain missions (Temp fix: use -nomusic)
- Techroom CTD
- Modular weapons bug
http://fs2source.warpcore.org/exes/latest/C20050221.zip
Edit: Forgot lightning thing.
Edit
Added to the website.//redmenace
-
what is this 'new trail code' I'm hearing so much about lately?
-
Trails use a one-way linked list rather than a statically allocated array with a free and used list.
-
is that faster!?
-
It depends. Memory has to be dynamically allocated, but it's not a whole lot; that's only when a missile is created, a ship is created in a nebula mission (or one with ship trails on), or a ship fires burners. (There are a few exceptions, like if a ship stops or flies slow). Creating a trail requires 2108 bytes of memory. (2k)
Once trails are created it will actually be faster, because everything is done via pointers (no more array indexing) and only one pointer needs to be changed when a ship is deleted.
It also means we won't have a 3 MB chunk of memory constantly devoted to trails (even if none exist).
-
is that why missile trails have started looking better?
-
Originally posted by WMCoolmon
- Some people have reported crashes with regard to warping out
- FS2 seems to freeze up randomly on certain missions
[/B]
Do you know if these issues are related? I had the same problem, and the random freezing/crashing and the jumpouts were very similar.
Anyway, keep up the good work, WMC. Hell, at this rate, you might fix the modular weapons bug this next month :nervous:.
-
I don't think they're related; the freezing bug seems to be caused by music, the warpout bug was determined by one person to be related to not having any background in a mission. I haven't experienced it recently, though.
As for missile trails looking better, I don't think so. (Although I wish I could say yes. :p) Missiles only have one trail, and I didn't touch any of the segment limits.
Hmm, modular weapons bug, I need to fix that.
-
Back from vacation. Testing this tonight :)
-
from your build:
Error: Unrecognized operator.
In sexpression: ( when
( true )
( toggle-hud )
( player-use-ai )
( don't-collide-invisible
"Alpha 1"
"Camera"
)
( cap-waypoint-speed
"EA Hyperion 1"
10
)
( cap-waypoint-speed
"EA Hyperion 3"
10
)
( cap-waypoint-speed "Camera" 50 )
( set-ship-facing
"Alpha 1"
( get-object-x
"EA Hyperion 1"
"turret09a"
)
( get-object-y
"EA Hyperion 1"
"turret09a"
)
( get-object-z
"EA Hyperion 1"
"turret09a"
)
)
)
(Error appears to be: toggle-hud)
File:.\mission\missionparse.cpp
Line: 4544
Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
-
a suggestion, perhaps, but how about a set-camera-path sexp? Currently, the only way to set a camera into motion is by 'dragging' it under a 'dolly' of sorts, using the set-ship-position sexps. But if we can get a ship to move from point A to point B, with the specified speed and WITHOUT having to face the direction of travel, it will improve upon the system tremendously, not to mention bypass the stupidity of the AI when it comes to travelling in a simple, straight line!!
-
This build seems to be tearing apart my table files, when older versions let it be (nothing wrong with the tables)
EDIT: Tearing apart as in giving me errors.
Dozens of these, I haven't gotten it to play yet.
---------------------------
Error!
---------------------------
Error: difficulty.tbl(8):
Error: Required token = [#End], found [1] .
File:.\parse\parselo.cpp
Line: 481
Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
---------------------------
Error!
---------------------------
Error: ships.tbl(2493):
Error: Required token = [#End], [$Subsystem:] or [$Name], found [$Trail:].
File:.\parse\parselo.cpp
Line: 481
Call stack:
------------------------------------------------------------------
---------------------------
-
It causes an error:
Error: Can't open file < FoD.pof >
File:.\model\modelread.cpp
Line: 1618
Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
fixed the brackets so the model name shows up //phreak
-
That's not really specific, nor does it distinguish itself from the cruiser03x.pof bug from the VP's. What were you doing when that came up?
-
Sorry, I was starting a mission which invlved a command brief, A Sathanas and a Colossus, I had the "All ships beam-freed by default" option on. Here is the ErroR in full:
(http://img.photobucket.com/albums/v517/kietotheworld/error.bmp)
-
What on earth is FoD.pof?
-
:lol:
That will definitely be fixed in the next build, I was just having a bit of fun with the new HUD automatic HUD shield display and forgot to take it out...
The table errors mean that you're missing a required variable. I made the parser stricter - it gives errors instead of warnings - because it does cause CTDs in some situtations.
Edit: toggle-hud is now hud-disable, that was changed by Goob; it also agrees with the rest of the Hud SEXPs that I added.
There actually already is code in there to handle cameras moving at a constant velocity in 3D space, but I haven't tackled the acceleration/decceleration code yet. I can add a set-camera-velocity though.
-
:wtf: That's no standard FS2 model. What mods have you got installed?
-
Am I missing something? What is it?
:nervous:
EDIT: Nevermind, looks like that's something WMCoolmon's been playing with. I'm guessing it's got something to do with ships with no defined shield ani, and something clever to make those look better.
-
It's not a mod... :nervous:
-
Originally posted by WMCoolmon
The table errors mean that you're missing a required variable. I made the parser stricter - it gives errors instead of warnings - because it does cause CTDs in some situtations.
The tables I'm using worked just fine, never caused any crashes, but this bug seems to think they're all messed up (they're fsport tables, minus Shivan entries and the fighters have a trail coming out of each of their engines). The difficulty.tbl that it keeps tearing apart is just the default one.
-
lol @ disable crashing
-
I can't seem to reproduce the error...can you post your difficulty.tbl and/or the offending ships.tbl entry?
-
I can't run this build. It performs illegal operation when I select it in the Browse window AND when I try to run it.
-
for some reason, the weapon models build is the only one that works reliably for me
-
Any more info than that, guys? :p
-
I told all I could. Command flags do not make any difference.
-
i'd post stuff, but instead of crashing to desktop as usual, the game just freezes the screen where it is, and i cant do anything after that
-
This is...odd, to say the least.
Recently, I've been observing that FS2 gives me a strange 'over-exposure' effect. I managed to stop this previously by removing the 'disable setting of gamma' field and then resetting the brightness.
Now it's back again, and it's making all my nebulas look like crap in FS2, while in FRED they look perfectly acceptable. If i try to run FS2 with the same .pcx's FRED uses, it still looks crap and super-exposed :ick:
And this is with TBP and all the TBP nebs. I've deleted the HDRish on my PC, but it's STILL like that :/
-
Over exposure is cool though! Did WMcoolman secretly implement it in this build? :drevil:
-
I've changed one thing (without the change it still does it), and it gives me an
---------------------------
Error!
---------------------------
Error: difficulty.tbl(8):
Error: Required token = [#End], found [1] .
File:.\parse\parselo.cpp
Line: 481
#Difficulty Settings
;; VE E M H I
;;--------------------------------------------------------------------
$Max Incoming Asteroids: 3 4 5 7 10
$Player Countermeasure Life Scale: 3 2 1.5 1.25 1
$Player Weapon Recharge Scale: 10 4 2.5 2 1.5
$Player Afterburner Recharge Scale: 5 3 2 1. 5 1
$Max Missles Locked on Player: 2 3 4 7 99
$Max Player Attackers: 2 3 4 5 99
$AI Turn Time Scale: 3 2.2 1.6 1.3 1.0
;;always link primary lasers if energy reserves are above this percentage
$AI Always Links Energy Weapons: 100 80 60 40 20
;;maybe link primary lasers if energy reserves are above this percentage and hull integrity is low
$AI Maybe Links Energy Weapons: 90 60 40 20 10
;;do the same thing with ballistic primaries
$AI Always Links Ammo Weapons: 95 80 60 40 20
$AI Maybe Links Ammo Weapons: 90 60 40 20 10
;;Seconds to add to time it takes for player's enemies to get in range.
$AI In Range Time: 2 1.4 0.75 0.0 -1.0
$AI Countermeasure Firing Chance: 0.2 0.3 0.5 0.9 1.1
$AI Sheild Manage Delays: 5 4 2.5 1.2 0.1
$Friendly AI Fire Delay Scale: 2 1.4 1.25 1.1 1
$Hostile AI Fire Delay Scale: 2 1.4 1.25 1.1 1 ;original 4 2.5 1.75 1.25 1
$AI Damage Reduction to Player Hull: 0.25 0.4 0.65 0.85 1
$AI Damage Reduction to Player Subsys: 0.2 0.4 0.6 0.8 1
$Max Beam Friendly Fire Damage: 0 5 10 20 30
#End
-
$Player Afterburner Recharge Scale: 5 3 2 1. 5 1
theres a space where is boldened
WM: can you make the strict parsing optional. this is going to cause some trouble.
-
I posted about the nebula thing here:
http://www.hard-light.net/forums/index.php/topic,30763.0.html
-
Wow...this build tore my tables to pieces, but what was annoying as hell at first turned out to be a necessary evil. Kudos for the picky parser.:)
-
Originally posted by Turambar
i'd post stuff, but instead of crashing to desktop as usual, the game just freezes the screen where it is, and i cant do anything after that
Ahh, that seems to be a problem with the music code since the Linux merge...turning off music seems to fix it for now.
Edit: WM: can you make the strict parsing optional. this is going to cause some trouble.
I'd rather not...I don't mind making more tags optional, if there are ones commonly skipped, but it's just bad programming practice to have it possible to skip fields that the parser assumes are going to be in there. I haven't noticed any problems with the FS2 main campaign, the Derelict re-release, Inferno SCP, STL/the port's tables, TBP, RR, DEM, the Aeos Affair, Lightning Marshal, or SoK. The BWO Demo does seem to have some problems.
-
WMCoolmon: Your build is screwing up the nebulas royally. See the above link for the pictures. The same nebulas work fine under previous taylor builds, so it must be that special feature you mentioned in the first post :P
-
It's not the special feature...AFAIK, no one's figured out how to even get to it. :p I've been messing around with the lowlevel image-showing code though, so it could very well be one of my multi-res changes.
-
Techroom!! I suppose I have the same problem as Raa....
Click techroom, CTD.
-
Edit: Ooops, wrong window :nervous:
Build is on the way, incidentally.
-
one question. is there a build without all the modifications to the low-res stuff, but with all the cutscene stuff? Will taylor's 01032005 have the cutscene stuff?
-
What do the No_crash and more realistic lighting flags do?
-
Originally posted by AqueousShadow
Techroom!! I suppose I have the same problem as Raa....
Click techroom, CTD.
Doh...
New pilot creation...:rolleyes:
Oh but uhh...I still can't play anything. Pressing commit locks up my game. It also seems that all my briefing and techroom anis are all slowed.
-
Originally posted by Singh
one question. is there a build without all the modifications to the low-res stuff, but with all the cutscene stuff? Will taylor's 01032005 have the cutscene stuff?
Not yet. A lot of these changes are specific to my build; I've been adding the occassional nonstandard res fix and updates to the lowlevel 2D stuffs to try and keep from completely outstripping CVS, but when I commit the cutscenes stuff it all has to go in.
I don't really understand what you mean by the low-res stuff. None of my nonstandard res fixes should effect the standard resolutions (although I don't test in 1024x768 much, so I could've missed a glitch I introduced) and all my nonstandard changes serve to move things where they should be - ie make the briefing icons stay on the screen and be clickable again, move the secondary recticule so if you aim with it you might actually hit something, etc.
-
Originally posted by WMCoolmon
I don't really understand what you mean by the low-res stuff. None of my nonstandard res fixes should effect the standard resolutions (although I don't test in 1024x768 much, so I could've missed a glitch I introduced) and all my nonstandard changes serve to move things where they should be - ie make the briefing icons stay on the screen and be clickable again, move the secondary recticule so if you aim with it you might actually hit something, etc.
by saying low res stuff I was actually meaning your res fixes actually. At least, the ones that were screwing up the backgrouds.
Apologies, I should have been more specific. The other stuff does work fine though, at the least.
-
Originally posted by kietotheworld
What do the No_crash and more realistic lighting flags do?
I agree... I tried the "No_Crash" option, but it told me that the No Crash has crashed, asked if I wanted to retry, then told me the retry failed and crashed. Its a feature worthy of Monty Python from what I can see. I also noticed a "fix mission" or something like that... what does it do?
However, this build gave me a CTD on commit (Derelic, BR Edition) without error message. I attempted it with the debug build, but it dropped to destop with an error message about not being able to open Thruster01 on the Pegasus pof for some reason... and we all know, that if you're dropped to the destop and FSO is minimized... good luck trying to resume the game. WMCoolmon, could you complie a new version of FRED with your next build? I doesn't have to have too many fixes, just the stricter error checking system so I can fix errors without having to run FSO itself.
-
The two new troubleshooting options do just what they seem to do. :D Realistic lighting works only in OGL, it changes the lighting somehow...I'm not sure how, exactly, but it can look pretty good: example (http://fs2source.warpcore.org/wmcscreenies/inferno/blueship.png)
The CTD is probably because of a missed check for trails existing in the trails code. I think I caught & fixed this after the last build I posted.
FRED is, atm, pretty much broken. I've been poking around, trying to get the rendering system working, but haven't had any success so far. If you still want a build I can give you one - it seems to mostly work, minus the main window of ships, but I haven't extensively tested it.
You can always run fs2_open windowed, or in OGL mode, which hasn't seemed to cause problems for me the couple of times I've had the window minimized. :nervous: Thank you for trying it with a debug build, though. :nod:
After looking through the relevant code for starfield-drawing, though, I can't seem to find any functions that I changed. Do any of taylor's other builds show that? Can you figure out when it occured? There is a huge space of time between 1/03 and now that the bug could have occured, esp. since the Linux merge was completed between then and now. (Is it occuring in both D3D and OGL?)
-
the bug doesnt occur with the C01292005 build. I haven't tried any of the Feb builds yet though...
-
Originally posted by WMCoolmon
-- Lock it? (False to unlock)
-- 0 for first-person, 1 for chase, 2 for external, 3 for top-down (optional)
Great!
-
Originally posted by Singh
the bug doesnt occur with the C01292005 build. I haven't tried any of the Feb builds yet though...
There's this random build (No idea where it came from, but whatever):
http://fs2source.warpcore.org/exes/latest/C02092005x.zip
There's taylor's build:
http://icculus.org/~taylor/fso/testing/20050212-win32.zip
Then there's the cutscenes build:
http://fs2source.warpcore.org/exes/latest/C20050218.zip
Oh, with further thought I'm going to leave that SEXP as lock-perspective, makes more sense since the force part is optional.
Edit: Also, my next build will feature the ability to edit ships.tbl flags without closing FS2, as part of the special feature. :D
-
Originally posted by WMCoolmon
New variables in mission file for jump node (see example)[/color]
Example:
$Jump Node: 1.0 3.0 4.0
+Jump Node Name: Dave's House o' Fighters ;;Technically a $ will work here too, it was the default, but a + fits in with the parsing scheme better, it is optional after all
;;New stuff
+Model File: FoD.pof ;;yes it works now
+Alphacolor: 255 0 255 255 ;;last variable is for alpha, ie transparency, 255 is full
+Hidden: YES ;;now you have to use show-jumpnode to make it show up[/color]
[/B]
Well... what's this all about, then? :p
-
The trails for the player and his wing/squadron seem to be drawn as white squares. If you aren't aware of a bug like this, I can be more specific and get some screens, etc.
-
I think I've seen this once or twice while testing, but was debugging something already and didn't focus much on it. What are the circumstances? If this is under OGL, it may be that the textures are not being loaded somehow (may be missing, or in jpg/tga formats and no -jpgtga is specified).
-
I'm using Direct3d, ATI Radeon 9000 Pro. What seems to happen is the players ship (no matter what class) draws engine glows as white boxes, but only on the highest LOD. It appears that the other ships don't have this problem, unless they're the same class as the player ship.
EDIT: In response to below post.:p
-
*In response to Solatar's last post*
This is regardless of ship class, ie it can't be a missing file? (So if you fly a myrmi, myrmis have trouble, if you fly a perseus, myrmis are fine but perseus have white-box trails.)
-
Correct, and I've tested with both .pcx and other files, as well as Vasudan and Terran.
EDIT: it appears that I was wrong, the player's "squadron" suffers. I've got Alpha and Beta flying Horus interceptors and Gamma flying Osiris bombers and all three wings have the issue. In another mission Alpha and Beta fly Valkyries, and they both have the issue, but no Horus interceptors in that mission do.
-
Can we expect in this build Shinemaps support for ATI cards with recent Catalyst Driver ??
-
Don't expect that with any builds until Bob gets his code thouroughly tested.
It's in Bob's local codebase, and not CVS.
So. no.
-
Is there a particular reason that this build disallows time compression?
-
Human logic error. :p
It'll be fixed in the next update.
Oh, has anyone tried using the techroom in debug mode?
-
Yeah, everything worked fine there and I didn't notice anything different.
By the way, does this line in the debug spew indicate that the game has exited?
31638 frames executed in 52072.008 seconds, 0.608 frames per second.
-
Originally posted by WMCoolmon
Oh, has anyone tried using the techroom in debug mode?
I just did and CTD. :p No error messages or anything. Just the default window's CTD message.
-
Originally posted by MetalDestroyer
Can we expect in this build Shinemaps support for ATI cards with recent Catalyst Driver ??
Shinemaps already work with the latest Catalyst drivers if you're using OpenGL.
-
i cant seem to get $Tech model: to work at all. another thing, what specifies the level of zoom on the 3d icons, alot of them are either zoomed to far and show almost nothing, others are zoomed in so close that you cant really tell what it is.anyone whos played the nukemod beta with one of your builds should be able to confirm this.
-
I CTD after a mission finishes loading. Works perfect up until then (unless I am using a mod [used TBP]).
-
Originally posted by WMCoolmon
There's this random build (No idea where it came from, but whatever):
http://fs2source.warpcore.org/exes/latest/C02092005x.zip
There's taylor's build:
http://icculus.org/~taylor/fso/testing/20050212-win32.zip
Then there's the cutscenes build:
http://fs2source.warpcore.org/exes/latest/C20050218.zip
Oh, with further thought I'm going to leave that SEXP as lock-perspective, makes more sense since the force part is optional.
Edit: Also, my next build will feature the ability to edit ships.tbl flags without closing FS2, as part of the special feature. :D
The overflare problem occurs as early as taylor's 20050208 build. That means it was commited rather early.