Meadville Space Center
Welcome, Guest. Please login or register.
February 28, 2020, 04:56:00 PM

Login with username, password and session length
Search:     Advanced search
25068 Posts in 2094 Topics by 2266 Members
Latest Member: twa517
* Home Help Search Login Register
+  Meadville Space Center
|-+  Project Apollo - NASSP
| |-+  Project Apollo - NASSP Development
| | |-+  Modeling (Moderators: movieman, Swatch, lassombra)
| | | |-+  Mesh performance optimization
« previous next »
Pages: [1] Print
Author Topic: Mesh performance optimization  (Read 6264 times)
Tschachim
Project Apollo - NASSP
Administrator
Hero Member
*****
Posts: 3700


nassp.sf.net


View Profile WWW
« on: June 07, 2007, 09:47:40 AM »

Hi 3D Artists and Apollo fans,

during the work on OVP/Orbitervis it turned out that the most important optimization (besides avoiding too many polygons) is to reduce the mesh groups of a given mesh as far as possible. This is also explained and confirmed by DanSteph in the Orbiter forum. For a non-animated mesh that means one group = one material, animated meshes need to retain the groups necessary for the animations, of course. If your mesh has for example 12 groups instead of 10 it's not that big deal, but the Saturn V interstage had 1419 groups instead of 4, which really was horrible.

I already optimized the following meshes:

  • High res Saturn V
  • Canaveral LC39 scenery (pad, VAB, crawler etc.)
  • CSM (except the work in progress VC)
  • Canaveral LC37
  • Parts of Canaveral LC34

so basically everthing you see in a Saturn V launch scenario, the optimization almost doubled my frame rate. I'll continue that with the remaining meshes (Saturn 1B, low res meshes, LM etc.) and post the progress here. Of course new meshes should be optimized as explained above, too.

Cheers
Tschachim
Logged

FordPrefect
Project Team Member
Sr. Member
****
Posts: 268



View Profile Email
« Reply #1 on: June 07, 2007, 10:03:18 AM »

Thanks for this vital information, Tschachim. I will keep this in mind with my projects*

I'll be curious on the FPS improvement on my old Pentium III 900 MHz, GeForce FX5200 128 Mb system!


*which are delayed big time, sorry. Expect updates at the end of this month (SIM bay + SaturnV textures)
« Last Edit: June 07, 2007, 10:06:48 AM by FordPrefect » Logged

My Project Apollo work in progress:
* New detailed Lunar Module Ascent stage with virtual cockpit (VC currently planned as eye candy only) 18 % done

My Project Apollo work to be continued:
* new Service Module SPS engine bell
* various Saturn V textures, exhaust textures
* SIM Bay for the SM


My long-term plans are to create a:
* New detailed Lunar Module descent stage (eventually models of all flown LM's)
* New F-1 engines for the S-1C stage showing the foil (batting) insulation
* New LUT and launch pad (if nobody else does it)
Zachstar
Sr. Member
****
Posts: 317

Is it Star Trek?


View Profile
« Reply #2 on: June 07, 2007, 05:45:18 PM »

The best FPS and quality Improvements will be from using the DX9/OpenGL clients optimized.

Thats where I hope Seth will focus his work on when he eventually starts working on the DX9 Client.

Thanks for the research!  Thumbs Up
Logged


-------------------------------------------
Tschachim
Project Apollo - NASSP
Administrator
Hero Member
*****
Posts: 3700


nassp.sf.net


View Profile WWW
« Reply #3 on: August 26, 2007, 12:19:26 PM »

I just committed the optimized meshes for the Saturn 1B, LC34 and both the low-res Saturn V and Saturn 1B. Now most of the meshes I'm aware of (except the LM) are optimized. Please report here if I forgot one!

Cheers
Tschachim
Logged

Eddie
Full Member
***
Posts: 56


View Profile
« Reply #4 on: August 27, 2007, 08:57:50 AM »

I like the look of the VC, especially the view up te tunnel! Are you working on the idea of using the tunnel to get to the LEM?
Logged
Swatch
Moderator
Hero Member
****
Posts: 1003


jasonims
View Profile
« Reply #5 on: August 27, 2007, 12:06:50 PM »

its a possibility, but just wait til you see the ACTUAL VC!  What you've seen so far was a prototype, testing the texture limitations and the mesh size requirements (that's a whole lot of points for those switches).  But trust me, you guys won't be disappointed. Cool
Logged

My Project Apollo Work:
CM Visual
 -VC (~75% complete: texture work beginning again; mesh-78%; texture-70%)
Propulsion Particle Improvements (Focused on S1B right now, BETA 1.0 has been commited)
New Docking Method (~50% complete: research complete; coding partially completed, testing not underway)

Future Work:  (if it's here, it's deemed unnecessary to upcoming release)

Older Work:  (if it's here, it's fair game to whoever wants to improve)
EMS Implementation (committed: minor flaws, but groundwork is there, needs extensive testing)
EMS scrolls (committed: not refined, but usable)
SM Visual (committed: mesh-finished, texture-60%; possibly revisited in future)
J2 Texture (commited: room for improvement)
LRV (committed: mesh-finished, texture-90%; in future a ground up rebuild may be in order, but not on my plans)
Eddie
Full Member
***
Posts: 56


View Profile
« Reply #6 on: August 27, 2007, 02:47:14 PM »

Looking forward to it swatch! Sounds like a ton of work though!! Happy
Logged
Swatch
Moderator
Hero Member
****
Posts: 1003


jasonims
View Profile
« Reply #7 on: April 14, 2008, 11:44:41 PM »

Ok, I've touched on it before, but I'm curious again....

I've seen the AMSO mesh, and while it is very pretty, its not completely accurate, so I'm continuing work on my VC.  But one thing stands out to me with the AMSO mesh...its got all the switches.  Now I was concerned that trying to do that would bog down a machine, but evidently I was wrong.  I'm trying to decide whether the optimum path is implement many copies of a single mesh through programming or have the switches built into the mesh itself....


So does anyone know if we'll take a bigger hit through coding it in or meshing it in? 

I look forward to neither, but its in the name of accuracy!
Logged

My Project Apollo Work:
CM Visual
 -VC (~75% complete: texture work beginning again; mesh-78%; texture-70%)
Propulsion Particle Improvements (Focused on S1B right now, BETA 1.0 has been commited)
New Docking Method (~50% complete: research complete; coding partially completed, testing not underway)

Future Work:  (if it's here, it's deemed unnecessary to upcoming release)

Older Work:  (if it's here, it's fair game to whoever wants to improve)
EMS Implementation (committed: minor flaws, but groundwork is there, needs extensive testing)
EMS scrolls (committed: not refined, but usable)
SM Visual (committed: mesh-finished, texture-60%; possibly revisited in future)
J2 Texture (commited: room for improvement)
LRV (committed: mesh-finished, texture-90%; in future a ground up rebuild may be in order, but not on my plans)
lassombra
Moderator
Sr. Member
****
Posts: 410


View Profile Email
« Reply #8 on: April 15, 2008, 12:54:45 AM »

I think we'll be fine with simply meshing it in and using simple animations on the switches...

programmatically switching between different meshes for each switch...  that sounds like a lot worse than a single mesh with animations.

If I don't understand what you're saying, then just ignore me.
Logged

My current Project Apollo work:

Quickstart to the Moon initiative (Quickstart_to_the_Moon): Done through earth orbit.  Working on new method of calculating TLI.

Checklist Controller: 
  • MFD Interface 99%(Minor cleanup and future features remain)
  • Panel Interface 99%
  • Excel interface and logic 99%
  • LEM Event code.0%
  • DSKY Interface code. Framework complete, creating "buttons"
  Approximately 80% done. (Checklist Controller
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!