Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Test Builds => Topic started by: Bobboau on March 12, 2005, 05:06:18 pm
-
http://freespace.volitionwatch.com/blackwater/fs2_open_Bobboau_3-12-05.zip
I would like someone to make/find a model with the most absurd number of thrusters on it posable, then fill a mission with as many as you can, and then run any of the recent (last week or two) builds, note your framerate, then run this build, note your frame rate, finaly come back here report your findings.
-
By thrusters to you mean engine subsystems or actual enging glowpoint thrusters?
-
glowy things
-
I didn´t do exactly, what you said (wrote), but i just tried "surrender bellisarius", which gave me 100 - 120 FPS most of the time using "older" builds like your WM-build. With the new one i have 25-30 FPS each time i have two or more ships in my reticle. This means a framerate drop to 25%. I am using Cat 4.3. Maybe it´s really an ATI specific problem. Aren´t there any NVidia guys out there, who can confirm this?
-
the wepon model build isn't recent enough.
try useing this one
http://fs2source.warpcore.org/exes/latest/C03122005.zip
an actual mission with fighting and stuff is going to have too many things going on to tell if this specific change is working or not, and if there arn't a lot of ships the diference will be too small to notice.
-
pf chimera has 10 thrusterpoints. id sugest making a mission for nukemod with about 50 of the little suckers. the way the things handel should make for an intresting furball :D
-
the wepon model build isn't recent enough.
So does that mean that the weapon model bulid is included in the recent "Tri-Build"?
-
But the weapon model build is fast an stable, much faster than all recent builds i´ve tested in the last four weeks. Ah...ok.. i think you opened this thread to test your new feature, so don´t take care of me ;-)
-
HENCE ME TRYING TO MAKE THE NEWR BUILDS FASTER
-
Mhhh... i really know what you´ve done (and you are doing) to the community. So what i´ve said was not to critizise you, it is just my opinion. I meant it, when i said "don´t take care of me" or maybe better "don´t take attention of my post" (english is not my native language)
-
ok first off I didn't realize that was in caps when I wrote it out, so I didn't intend to yell, the point of this thread is an atempt to address the recent slowdown that has been plageing recent builds, so your telling me that the weapon model build is better doen't help me any, becase I know this, I'm trying to corect the problem in all recent builds.
second, I just want someone to do a simple couple of tests, to see how much if any benefit my new geometry batcher is dooing. just someone, anyone who has a working version of Fred plop in about a hundred (/*thinks of a ship with a lot of thrusters*/) tritons all lined up in the same general direction and in a positon were you can see all of them at the same time from behind. use my new build and tell me what the diference between it and any other build relesed in the last week or two (like this one (http://fs2source.warpcore.org/exes/latest/C03122005.zip)) is, imy new build should be faster at least by a bit.
further, I have another new build
http://freespace.volitionwatch.com/blackwater/fs2_open_Bobboau_3-14-05.zip
wich should have better performence in combat (made some improvements with the laser rendering code.)
-
This latest build crashes at start up for me. Missing vorbis er somthing/
-
Make sure you're not using OGL, Bobb's builds often dislike it.
-
no it's those damned vorbis dlls he's haveing problems with.
I have yet another build, this one has particles sped up quite a bit, this should make for far more reliable framerates in mission, it isn't perfict though. but do tell me if frame rates seem to be moveing in the right direction.
http://freespace.volitionwatch.com/blackwater/fs2_open_Bobboau_3-14-05a.zip
-
try these dlls.
-
Originally posted by Bobboau
no it's those damned vorbis dlls he's haveing problems with.
Can't remember if anyone else asked or not but why don't you just static link it? There's no license issue with that and it saves you from giving out the dlls.
-
well, I sure do hope what I did helped things cause its'a go'n in.
thanks alot guys, realy. nice to know you can be depended on :).
-
I would have tested this sooner, but i was flooded with work. Finally got to test it and i have only one thought on the matter:
:jaw:
I put 30 high poly tritons into one mission - which adds up to 179070 polys visible at one point in time, and 510 glowpoints all visible to the player. The triton also uses a 2048x2048 res texture, along with 1024 res glowmaps and shinemaps.
The C03122005 build managed to average about 10-15FPS. This would drop right down to 2FPS when particles are displayed in force (strafing a hull).
Your 3-14-05a build managed to average 80-90 FPS. Even with particles. That's a hands down success right there. :D
Congratulations man. :yes:
-
well then, good :)
thank you!
this is in CVS, so you can look forward to this in all future builds.
-
Wow, that sounds...amazing. Gotta try this.
-
*downloads*
-
:doubt: :eek2: people are testing it.. :wtf:
...welll, you all seeing similar results?
-
I'm getting near 120fps in 20 fighter furballs. The inclusion of the 24 rotating turret BSG drops performance to 10 fps.
-
is that better or worse than before?
you mentioned there were problems with the turrets.
and you are useing th 05a build, right?
-
where does these DLL's go?
-
Usually just in the same place as the exe.
-
I figured I'd post this here, since this is the latest thead started by Bob in the new builds subforum. I was playing around with external weapons yesterday and noticed that when it comes to how many missiles to display externally, the code seems to override bank cappacity in favor of number of firepoints. Basically, I've got an Apollo with an external bank with 3 firepoints (1st under centerline, 1 under each nacelle). I've got bank cappacity set so that it can carry either 3 MX-50's or 1 Phoenix V, but if I set a Phoenix as the loadout for that bank, it renders one on all 3 firepoints. Obviously, that shouldn't happen. Displayed external secondary weapons should match the cappacity of that bank (unless, the cappacity for a selected secondary exceeds the number of firepoints for that bank), starting on the 1st firepoint in that bank. I haven't tested this with WMCoolmon's "ex" build yet, but I thought I'd post this here before I forgot.
Despite this, it did work, and it was the first time I got bank-specific loadouts to function properly.
-
were you useing the first build in that thread or the later one that was suposed to fix this?
-
That was using your March 12 build. I think I also tested it with WMCoolmon's March 18th build. I'll try it with your 14a build and WMC's ex build tonight.