Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Test Builds => Topic started by: Goober5000 on November 06, 2004, 02:06:38 am
-
New build, with the most recent code in CVS. Not much new here, but it was compiled with speech support and it includes a few bugfixes. Same caveats about taylor's stuff as in the 20041102 thread.
http://fs2source.warpcore.org/exes/latest/20041106-Goober5000.rar
-
It is good that FRED's brightness problem was fixed. I will be able to test the build any deeper this afternoon.
[EDIT]It's already afternoon here. :D
-
Urgent, I thing communication with the wingmates is busted.
I created a new pilot played 2 missions on easy
then created another one. Result is the same...
when you press "c" the ONLY option you have is to call the support ship to rearm.
The only thing different to a custom install is the Lightspeeds' latest maps (v11) and lights (v8). Also voice is enabled throughout (and works too!)
Can anyone confirm this?
-
If you can hold on for a few minutes, sure . . .
[EDIT]Can't confirm that. I can give orders to my squadmates.
But I discovered something: My ship tech database is quite weird: I can only see the Ulysses, the Erinyes from the Terrans, nothing from the Vasudans and almost all Shivans. However, in-game, all the ships work.
-
GT-K: in the first 2 or 3 missions, that's normal. Try using the -allslev tag and a mission from the techroom from later on in the campaign.
-
Originally posted by GT-Keravnos
Urgent, I thing communication with the wingmates is busted.
I created a new pilot played 2 missions on easy
then created another one. Result is the same...
when you press "c" the ONLY option you have is to call the support ship to rearm.
The only thing different to a custom install is the Lightspeeds' latest maps (v11) and lights (v8). Also voice is enabled throughout (and works too!)
Can anyone confirm this?
if you' mean the first 2 missions of the main fs2 campaign.. yes I can confirm that, but for as far a I know, it's supposed to be like that.. in the first missions, you're not leading your wing, so you can't gibe orders.
-
I don't know if I remember correctly, but you can give a few type of orders to your wingmen. i think the 'Form up on my wing' or 'Cover me' is available from the beginning.
[EDIT] I am wrong, you cannot give orders to wingmen in the first two missions.
-
*creates new pilot and checks*
well, at least not in the first mission.
-
Originally posted by kasperl
GT-K: in the first 2 or 3 missions, that's normal. Try using the -allslev tag and a mission from the techroom from later on in the campaign.
OOPS, I had forgotten about that, both the inability to order your wingmates, AND the -allslev tag. I think everything is a ok, except that foot in my mouth :D
and after that unfortunate "cry wolf" debacle for which I apologize :nervous:
I must say yet again "Thank you" to Taylor, Goober and the other coders for FINALLY eliminating one of the worst bugs in FS2, that most of you don't even know.
If you press the asterisk on the numpad, you will enter 3d person action where you see your fighter/bomber from the back, while it blows away the shivan threat. Up until now that mode was shaky to say the least with various problems none of which are really important right now because they are fixed. It works flawlessly, ebbs and flows like it should. I messed with it in approx. 10 missions the latest of which was clash of Titans 2.
Only on ONE single occasion did the bomber became "glued" to the center of the screen and even there, with a small dosage of afterburner it continued ebbing and flowing.
It was a personal request to Taylor (however many people might have wanted this), and thus is my personal "THANK YOU" note. I owe you a beer, or a beer case even. THANK YOU AGAIN.
-
I think I found a problem with one of the new sexps. It looks like disable-hud-except-messages doesn't disable the radar or the targeted ship data. But when I use both disable-hud (or Shift-O) with disable-hud-except-messages, the hud goes away, the messages still show, but the comm anis don't.
-
Bah. Mantis it.
-
Done.
-
I am getting the same problems Trivial Psychic reported in this (http://www.hard-light.net/forums/index.php/topic,27567.0.html) thread.
-
Yes, that problem is still present. This started around the time that the default warp display was changed from the 3D effect (if the model is present) back to the 2D effect. All new FRED builds have a checkbox in the mission specs editor to enable 3D warp for a mission, which replaces the checkbox to enable 2D warp that was present in older builds. I've created a few missions which have the 3D warp enabled and tested them under these builds, and the effect worked perfectly without any missing bits, so this appears to be restricted to the 2D effect. I've suggested that a -3D_warpeffect launcher flag be added so that we don't have to extract all the existing missions from the VPs and alter each one to get the 3D effect, which should also repair the effect problem, unless a player insists on using 2D.
Later!
-
It does not make sense to include the 3D warp.pof as a default in the SCP VP files and then require a check-box in each and every mission to be activated in order to render it properly.
This is a improper implementation of the backwards-compatibility principle. It doesn't "keep things like the original FS2." It breaks missions.
I strongly suggest that on this issue, a command-line option, and not a per mission checkbox, is the right way to go.
-
Oh and i thought this Missing Warp Sequence was a problem at my System.. but now it's clear.. it's a "bug".. i hope this will fix soon.. it's a litte annoying then 75% of all Warps are "Incomplete"
EDIT:
And the 3d Warp Effect looks better than the 2d Version ;)
-
Having only recently given this one a spin, I've discovered that if you alter the weapons loadout on a capital ship (i.e. fitting additional flak cannons on a Deimos' prow turrets [#s 21-24] ) a ship of the same type that appears later in the shiplist in the mission will have its armament supercede any previous instance of that ship class. It was rather alarming when I had a corvette sitting lobbing Subach fire from its forward turrets start spraying the area with TerSlash fire when another corvette of its class entered.
-
Originally posted by GT-Keravnos
Urgent, I thing communication with the wingmates is busted.
I created a new pilot played 2 missions on easy
then created another one. Result is the same...
when you press "c" the ONLY option you have is to call the support ship to rearm.
The only thing different to a custom install is the Lightspeeds' latest maps (v11) and lights (v8). Also voice is enabled throughout (and works too!)
Can anyone confirm this?
You're not allowed to order your wingmen in the early missions.
-
Originally posted by wolfdog
if you' mean the first 2 missions of the main fs2 campaign.. yes I can confirm that, but for as far a I know, it's supposed to be like that.. in the first missions, you're not leading your wing, so you can't gibe orders.
Originally posted by GT-Keravnos
OOPS, I had forgotten about that, both the inability to order your wingmates, AND the -allslev tag. I think everything is a ok, except that foot in my mouth :D
and after that unfortunate "cry wolf" debacle for which I apologize :nervous:
See? Already clarified.
-
WHITE SQUARES:shaking: there they are again. I know, we had that problem a few builds earlier, but now they are back. In FS2 Main campaign "the sixth wonder" e.g. Right after the start of the mission you can see it directly in front of you. Does anybody have seen them, too?
btw sys specs are radeon9800/pro + cat4.4
-
what graphics mode are you using?
what command line options are you using?
-
Hey, would you rather us report bugs here or on Mantis? I have found a few and would like to start helping out finding bugs.
-
Report all your @!*$ing bugs to Mantis so we can @!*$ing fix them
-
PhReAk, take a break. :)
-
im just quoting my sig :)
-
:D
-
So is anyone going to deal with the warp.pof problem? I really, really think that the player's decision to install the 3d warp.pof is all that is necessary. Making the mission designers go and change a setting in every single mission in order to use it is ridiculous. Especially since installing the 3d warp.pof breaks the original campaign missions under this system! It is like requiring us to go and change a setting in every single mission to use Lightspeed's new nebulae, instead of just installing them and setting the command line argument.
-
*Seconded*
-
I'm working on the warp thing now. It shows up fine in OGL so it's something in the D3D code I beleive. I will put in a cmdline option to use 3d but it's going to stay with the 2d version by default. If I get it fixed tonight I'll go ahead and release a new build since there have been a number of other fixes since the 20041106 build.
-
Eeexxccellleennnnttt!
-
Thank you, sir. :)
-
Alright it's fixered. Cmdline option is "-3dwarp" but will probably be depreciated when I get the time to finish in SCP options screen and move it there. No build for a while yet though.
-
Okay, just tested this build (had it on my HDD for some time, but did not find the time) with Sol: A History, a campaign for Inferno R1. In one mission, I ran into the problem with sudden crashes back to the desktop, but I couldn't track the problem down and was able to finish the mission the fourth or fifth time. The only real problem I ran into was the warp effect sometimes not able to decide wether to show that 'tunnel'-thingie or that trekish white effect. But otherwise, no problems. :yes:
-
this crashes on my pc before it does anything other than changing the screen mode and sticking my mouse to the corner of the screen. here's all the debugger outputted:
Setting language to English
soundcard = DirectSound
** MAX_CHANNELS set to 17. DS reported 17.
No sparky_hi_fs2.vp in directory C:\games\freespace2
GR_CPU: Family 6, MMX=Yes
Window in debugging mode... mouse clicking may cause problems!
Alpha texture format = ARGB, 4:4:4:4
Non-alpha texture format = ARGB, 1:5:5:5
D3D_32bit 1, bits_per_pixel 32Direct3D Initialized OK!
it starts then stops about 10 seconds later, but doesn't actually show anything at all. my system specs are:
celeron 1ghz
sis onboard gfx adapter, either 8 or 16 meg ram
256 mb sdram
sorry it's not much to go by... :-(
-
gees, not much ram atall. what are your vurtual memory settings?
I'm afraid your not going to get much out of this till you get a real graphics card and more ram.
-
virtual memory:
min 360 mb
max 720 mb
i think i can probably increase this a little, ive got an 80 gb hd w/ 30 gigs free, but im not sure
i know about the gfx card, but all the new ones need huge power supplies and ive only got around 150 watts and they need 300 or more. so until i save enough money to build a new one, im stuck with this one.
-
May I suggest a radeon 9600 pro
http://www.pricewatch.com/h/prc.aspx?i=37&a=5591&f=1
http://www.pricewatch.com/h/prc.aspx?i=37&a=5162&f=1
-
I think Nvidia cards are better for FS2_open as they do not have problems with the shinemapping with new driver versions.
So you don't have to decide whether you want to play new games or FS2_open with shine maps.
Other than that, ATI cards are great.
-
I'd try getting a gig of virtual memory at least, FSO has (depending on what enhancements you have downloaded) more than three times as much texture data being used
-
couple problems getting a new gfx card: this motherboard doesn't have any agp slots, it has onboard agp gfx, and like i said, the power supply is really small. guess i'll have to wait until i can get a new computer for better gfx :-(
and i set the vm to 1 gig min 2 gig max but it made no difference, still nothing happened.
the pf usage doesn't look to be to problem though, according to task manager pf usage never got beyond 50%.
-
Perhaps a GF FX5200 or a Radeon 9200 would work then, as they both have PCI versions IIRC.
-
looks like that card needs at least 250w though...
-
Ach, buy a new PSU; should be able to get one for about, I dunno, £20-£40 if you shop around :)
Not too pricey, in other words. Depends how many bells & whistles you want with it (super quiet or that sort of rubbish).
-
I wouldn't go any lower than 400W though. If you want to save a few bucks, go for Fortron. They're basically Antec power supplies sold at a lower price.
btw, does this build muck with the brightness on other machines? Granted, the last build I ran was the 20040822 build (which ran perfectly fine) When I run this build, its like I set the brightness/contrast to zero. When I exit FS2_Open, windows is the same way. I have to restart windows just to get the brightness/contrast back to where its supposed to be. Even if I set my monitor's b/c to 100%, its still too dark. The 11/02 build has the exact same bug.
command line options:
-spec -glow -d3dmipmap -ship_choice_3d -nomotiondebris -orbradar -d3d_no_vsync -nobeampierce -fps
XP SP2
Athlon XP 2800+
Leadtek K7NCR18D Pro (latest drivers)
512MB PC2700 (2x 256 in dual channel mode)
PNY Geforce 4 Ti4600 (128MB DDR) running the 61.77 dets
-
About the weird warp bug, I changed my fov setting (-fov) in the command line to .55 (I don't think the value has anything to do with it.)
and it fixed the cut off warp image bug and the trekkie looking one. It's still in 2d, but it doesn't look so funny.
Would someone else try this out, just to make sure I'm not crazy?
-
Originally posted by Vertigo1
btw, does this build muck with the brightness on other machines? Granted, the last build I ran was the 20040822 build (which ran perfectly fine) When I run this build, its like I set the brightness/contrast to zero. When I exit FS2_Open, windows is the same way. I have to restart windows just to get the brightness/contrast back to where its supposed to be. Even if I set my monitor's b/c to 100%, its still too dark. The 11/02 build has the exact same bug.
Using OpenGL it has changed the way the gamma is set and the default is really dark. It deffinitely shouldn't still be dark when you exit the game though. You can try setting the gamma slider in the options to 1.00 which will disable any visual change. If you are using D3D then I'm not sure what the problem is.
-
Disregard my last post!
In my excitement I failed to test that properly!:wtf:
When I played a mission I was greated by a very out of place Trek looking thing.
I think I'll leave the troubleshooting to those much olde and wiser than myself.
-
Originally posted by taylor
Using OpenGL it has changed the way the gamma is set and the default is really dark. It deffinitely shouldn't still be dark when you exit the game though. You can try setting the gamma slider in the options to 1.00 which will disable any visual change. If you are using D3D then I'm not sure what the problem is.
*smacks forehead*
I am using OpenGL. However, the gamma slider has zero effect on anything. It remains dark no matter what I do.
-
Originally posted by Vertigo1
I am using OpenGL. However, the gamma slider has zero effect on anything. It remains dark no matter what I do.
Strange, I've got the same card and have not had a problem. Make sure you've set the slider to 1.00 and then accept the changes, exit the game and restart your computer. If it still goes dark after you try the game again then I'm not quite sure what's going on. You could try updating the video drivers just in case. If that doesn't help any let me know.
-
Maybe you can try to activate "Disable D3D Gamma" in the Launcher.
It's under "Troubleshoot".
-
Originally posted by Overlord
Maybe you can try to activate "Disable D3D Gamma" in the Launcher.
It's under "Troubleshoot".
Good idea, wish I had thought of it when I made the gamma code change. ;) I just changed it last night to respect that setting for OpenGL but in this build it doesn't help any. I also changed it to reset to the no change default (1.0) when you exit and use the same registry setting as D3D. This will hopefully fix it all the way though I honestly don't know how it got through testing. I still think a driver issue may have attributed to the severity of Vertigo1's problem but it shouldn't be an issue in future builds.
-
Originally posted by taylor
Good idea, wish I had thought of it when I made the gamma code change. ;) I just changed it last night to respect that setting for OpenGL but in this build it doesn't help any. I also changed it to reset to the no change default (1.0) when you exit and use the same registry setting as D3D. This will hopefully fix it all the way though I honestly don't know how it got through testing. I still think a driver issue may have attributed to the severity of Vertigo1's problem but it shouldn't be an issue in future builds.
As for it being a driver issue, I seriously doubt it. I even rolled back to the previous set of drivers and this build still had the same gamma issues. Even the default Microsoft GF4 driver made no difference. However, none of this explains why the 8/22 build doesn't have this trouble so its obviously not my end.
Setting gamma to 1.0 made little difference, other than I have to set b/c to nearly 80 just to see anything like its supposed to be.
Perhaps if I were to test that new build to see if the problem disappears?
ICQ: 168701920 (already have you added)
-
I seem to be having a little trouble with this build. In particular, when playing through the FS2 main campaign, whenever I reach the first TAG mission, the game crashes to desktop when the mission ends. This happens whether it's a succesful completion, or if I fail/get blown to pieces and try to restart or exit to the briefing/hall.
-
Originally posted by Vertigo1
However, none of this explains why the 8/22 build doesn't have this trouble so its obviously not my end.
The 8/22 build didn't have to code in question which is why it works. A setting of 1.0 is supposed to apply no gamma changes so that points to an issue that will still hurt with the newest fixes since it defaults to 1.0. The cmdline option would have to be used to avoid the new code but the current builds don't support this.
Originally posted by phatosealpha
...when playing through the FS2 main campaign, whenever I reach the first TAG mission, the game crashes to desktop when the mission ends.
Go into the hud configuration screen before you start that mission and turn off the talking head box in the upper left. If that gets you through the mission then you can turn it back on. This is because of a large memory leak fix but because of some memory corruption somewhere it can crash on Windows. That's the only mission in the main campaign I know of that has the crash though. If you play FSPort you will have to do the same thing for the "Enter the Dragon" mission.
-
i guess i'm getting a new computer for christmas
http://support.dell.com/support/order/details.aspx?c=us&l=en&s=gen&order_number=100317926
hopefully it will be able to handle it :-)
-
Dude, Don't get a Dell :p
-
Get Alienware!
-
Originally posted by c_n00b
i guess i'm getting a new computer for christmas
http://support.dell.com/support/order/details.aspx?c=us&l=en&s=gen&order_number=100317926
hopefully it will be able to handle it :-)
Speaking as someone thats actually worked on Dells in the past, I can honestly say that the newer models are pieces of utter garbage. I could go into a long-winded rant on how horrible Dell has gotten over the years, but by the time I typed it all up the board would log me out automatically. ;) Suffice it to say, they use cheap retention methods instead of doing things like they should have from the beginning. For instance, the only thing holding down all the peripherials in the PCI and AGP slots is a little plastic lever. There are NO screws at all. If that plastic lever were to dry-rot and break...good luck keeping those cards in those slots securely. The heatsink retention method is severely lacking to say the least. One good thump on the case and the damn thing falls off! They don't even use a damn fan on the thing! The only thing keeping your processor from overheating is a cheapass plastic shroud covering it, which leads to a very slow outlet fan (the only fan in the case, not counting the one in the power supply). They're even so cheap that they slap in PC2100 DDR (266MHz effective) instead of atleast PC3200 (which would match the processor's FSB if its an older P4,) which only cost them what...a couple dollars more? Way to go Dell... :rolleyes: This may not mean anything to you, but using slower RAM hinders your performance greatly. Its like sticking a 3 cylinder engine into a full-size pickup. Sure, it'll work, but it'll take you forever to get anywhere. Lastly, their wiring methods are completely sub-standard. The power and ribbon cables are strewn all about the case, which not only hampers what little airflow you might have, but it looks like ****!
If you think Dell is bad after reading this, HP and Compaq are even worse offenders! Atleast I have some room to work with in a Dell. HP and Compaq cram everything together so damn tightly that I have to remove 80% of what's in there just to get at the RAM! The airflow is so minimal that if its running in a dusty environment, be ready for overheating issues.
Alienware...you get charged three to four times what it would cost to build the damn thing yourself! Alienware is so overpriced, its rediculous. Its like buying a Toyota at the price you'd normally pay for a Mercedez. The only thing they're good for is picking out parts for yourself, and then shopping around for the best price.
-
Which is why my PC is built 60% out of second hand parts and from salvaged pieces of other stuff....along with cheap equipment from India :D
-
did you read the description?
1 1 311-3621 512MB DDR2 SDRAM AT 400MHZ - 2X256MB,DIM
1 1 221-5230 DIM 4700,P4,530 (3.0GHZ),HT,INT SNDNICV
are you saying the "400 mhz" memory is only 266 mhz effictive? :-/
-
Originally posted by Vertigo1
Speaking as someone thats actually worked on Dells in the past, I can honestly say that the newer models are pieces of utter garbage. I could go into a long-winded rant on how horrible Dell has gotten over the years, but by the time I typed it all up the board would log me out automatically. ;) Suffice it to say, they use cheap retention methods instead of doing things like they should have from the beginning. For instance, the only thing holding down all the peripherials in the PCI and AGP slots is a little plastic lever. There are NO screws at all. If that plastic lever were to dry-rot and break...good luck keeping those cards in those slots securely. The heatsink retention method is severely lacking to say the least. One good thump on the case and the damn thing falls off! They don't even use a damn fan on the thing! The only thing keeping your processor from overheating is a cheapass plastic shroud covering it, which leads to a very slow outlet fan (the only fan in the case, not counting the one in the power supply). They're even so cheap that they slap in PC2100 DDR (266MHz effective) instead of atleast PC3200 (which would match the processor's FSB if its an older P4,) which only cost them what...a couple dollars more? Way to go Dell... :rolleyes: This may not mean anything to you, but using slower RAM hinders your performance greatly. Its like sticking a 3 cylinder engine into a full-size pickup. Sure, it'll work, but it'll take you forever to get anywhere. Lastly, their wiring methods are completely sub-standard. The power and ribbon cables are strewn all about the case, which not only hampers what little airflow you might have, but it looks like ****!
If you think Dell is bad after reading this, HP and Compaq are even worse offenders! Atleast I have some room to work with in a Dell. HP and Compaq cram everything together so damn tightly that I have to remove 80% of what's in there just to get at the RAM! The airflow is so minimal that if its running in a dusty environment, be ready for overheating issues.
Alienware...you get charged three to four times what it would cost to build the damn thing yourself! Alienware is so overpriced, its rediculous. Its like buying a Toyota at the price you'd normally pay for a Mercedez. The only thing they're good for is picking out parts for yourself, and then shopping around for the best price.
I couldnt have said it better. I have worked on many Dells in the past and here is what I have learned. Dells used to be fine computers but they have gone VERY FAR DOWN HILL in the last couple of years. WTF are they thinking when they put only 128 of RAM (even shared with the graphics) in their economy model. With that much ram the comp can barely boot!!! Then there is the integrated graphics issue that totally ****s those 128 RAM computers up. The minimum shared RAM you can set the graphics level to is 64 mb. This leaves you with only 64 mb (128 - 64 = 64) of system memory. Pieces of crap. The ones with integrated dont even come with an AGP slot!!! I dont see how they let such pieces of crap leave their factory. Almost all of them are completely un-upgradeable Just dont get Dell. Build your own (look online, there are a lot of good things that can help you out). Heck, I may even be able to help you out a little....
-
you express my frustration very well
-
still, it'll be way better than what i have now. not to mention, im not the one paying for it, so even a dell's a pretty big value at $0.
-
Originally posted by c_n00b
still, it'll be way better than what i have now. not to mention, im not the one paying for it, so even a dell's a pretty big value at $0.
Dude, take it from someone that knows better. You will not be happy with that machine. If you aren't willing to build it yourself, shop around at the local stores. Set yourself a budget of what you're actually willing to pay for the machine, build yourself a parts list and see what the local shops will sell it to you for. Remember, local support is always preferable. Also keep in mind that Dell, Gateway, Compaq, HP, and all the others do not have tech support call centers here in the US. When you call them for help, your call is being rounted all the way out to India to some guy making maybe $5 an hour that barely knows how to turn the damn things on. Everything they tell you is written down for them on a sheet of paper. If what you ask them isn't on there, the first time they'll tell you to do is use the system restore disk. :rolleyes: Furthermore, if you ever have the thing serviced by an "authorized dealer", they automatically run system restore disk to restore the computer to "factory conditions". The thing is, they don't tell you this beforehand, so any data you had on there is gone.
-
Oh yea. I have had that crap before. They make you pay extra tof the actual tech support. They kill all of the problems that they cant fix with a sledgehammer which is reformatting. God, I hate that crap.