Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Test Builds => Topic started by: WMCoolmon on June 26, 2004, 04:25:48 pm
-
Re-posting this from VW...
(http://fs2source.warpcore.org/exes/latest/fs2_open_C06252004.jpg)
The Build (http://fs2source.warpcore.org/exes/latest/fs2_open_C06252004.zip)
Target info
To enable target info next to the currently targeted ship, use command line "-targetinfo" (should appear in Graphics options)
This is something I came up with when trying to pick off a wing with my trebeuchets...it came out as good as could be expected, I'm particularly proud of it.
The new escort list
To enable an escort list of more than 3 ships, add "$Max Escort Ships:" then the number at the top of hud_gauges.tbl.
The absolute max is the same as the number of maximum shown/unshown entries in the list - currently 20.
In the default position in 1024x768, more than 16 will overflow into the weapons gauges.
You can now screw around with the escort list with hud_gauges.tbl! See below
#Main Gauges:
$Resolution: (1024 768)
$Escort List: (865 330) ;Where the escort list goes.
+Image: escort1
+Text: Monitoring ;This is incorrect, but how it is in the current build...will be fixed
#End
#Gauges
$Resolution: (1024 768)
$Escort List
$Header Text: (4 1)
;+Text: Monitoring ;This is correct, and how it will be after this build
$List: (0 13) ;Where the list starts
$Ship: (0 11) ;An individual entry
+Image: escort2
$Last Ship: (0 11) ;Last entry
+Image: escort3
$Ship Name: (4 0) ;Where the name goes relative to the entry position
$Ship Hull: (116 0) ;Ditto for hull %
$Ship Status: (-11 0) ;Ditto for ship status, aka the D that shows up when a ship is disabled.
#End
-
SourceCoolProject? :p
-
Actually, that's pretty close to what I usually mistake it for... ;)
-
That code you posted would be sufficient to create an entire, working hud_gauges.tbl file, correct?
-
Yep.
Every section and entry in hud_gauges is optional, although you have to head things with $Resolution or $Default or (In the ship gauges) $Ship.
Currently there's five sections, 1 variable. Expect to see this change though, hopefully by 3.6.1 I'll have a stable, efficient system finished.
$Max Escort Ships
#Custom Gauges
#Main Gauges
#Gauges
#Main Ship Gauges
#Ship Gauges
More info is in Bobboau Birthday Build.
-
Dude, this kicks ass! Love it! Wanna post/mail me a higher quality JPG of a clear screenshot so I can highlight this? :)
-
small question, but is it possible to return to the old explosion system with this build? I experience MASSIVE slowdowns whenever something goes boom, before it speeds back to normal. I'm currently using the full media vp file, but I dont want to extract anything since I have only 400MB left :/
Also, strangely, the original FS2 missions have no secondary weapons for the player to select. I've tried extracting the original missions again from the VP, so hopefully that should fix it...
-
*beats himself to the point of unconciousness for taking a break from the forums*
I can't believe I almost missed this stuff! :yes2:
-
For Setekh and everyone else:
Image gallery directory
http://fs2source.warpcore.org/exes/latest/gallery
Edit: Singh - if you've got enough space to copy the media VP, open the file in VPMage and delete the explosion files, build your modified VP, and delete the old one.
Make sure to test the new VP before deleting the old one though.
Edit 2: The bug where targeting a weapon generates a random weapon name is known and will be fixed in the next build.
-
ugh. you really, REALLY need to improve performance. It took me 1+ hours just to play FOUR missions because of the #@$*#$ loading time. I disabled glowmaps and PCX32, and have most of the fast options loaded, but its just annoying. Whenver a ship comes in and out, the slowdowns become worse. It's also quite bad when Flak is present, my FPS hits 2 in those cases, zooming all the way from 120 (im running 640x480x32), and sometimes for almost a minute the screen wont move, loading the next frame.
Also, a bug appears to be in the code that wont let me select secondaries other than in missions where they have been awarded
SCP looks good, but it sure as hell doesnt PLAY good. :ick:
-
Is that just in this build? :nervous:
Do you know when all these slowdowns started?
-
Originally posted by WMCoolmon
Is that just in this build? :nervous:
Do you know when all these slowdowns started?
Not really....i only recently started playing FS2, as opposed to taking random screenshots. The loading issue has been there quite a while, but it was ok in some of Bob's builds (the old ones where he fixed something) but 3.6 and after that has resulted in even worse slowdowns.....
They got worse in your last build (the C15062004 one). The loading time got longer with this one, but the FPS is still the same. Strangely, despite preloading mission sounds, it still slows down everytime a voice file is played, as if it's loading it again, the same with music and stuff.........
-
Yeah, I've had the same problem with all the builds since 06/07/04.
-
This build makes FreeSpace 2 crash to desktop as soon as I try to play a mission. The briefings are fine but there is this blue outline on the briefing map.
-
This build breaks multiplayer LAN on my machine. It will immediately CTD after the mission countdown timer is finished.
-
if the -targetinfo flag is set, perhaps you should move the distance underneath the ship type so it looks more uniform
-
Is there going to be a tool for making up the HUDs? Because I'd love to customize them, but I'll be damned ifI can figure out the pixel coordinates.
Also, will the hud_guages table be modular too?
-
It should already be modular. Look in Bobboau's birthday build for the stuff, and note that the HUD is currently in a transitional period. I am looking into making DRASTIC changes in the way the HUD is handled by the game.
Edit: BTW, if you want to figure out where pixels are, just open up paint. In the status bar it tells the current position, you can copy/paste gauges from a screenshot if you like.