Author Topic: Optimization: GPU-based Submodel Transforms  (Read 5131 times)

0 Members and 1 Guest are viewing this topic.

Offline Macfie

  • 210
  • If somebody made a campaign I've probably got it
Re: Optimization: GPU-based Submodel Transforms
Where does the patch file go?
Normal people believe that if it isn't broke, don't fix it. Engineers believe that if it isn't broke, it doesn't have enough features yet.
The difference between Mechanical Engineers and Civil Engineers is:
Mechanical Engineers build weapons.  Civil Engineers build targets
An optimist sees the glass half full; the pessimist sees it half empty. An engineer sees that the glass is twice as big as it needs to be.

 

Offline Fury

  • The Curmudgeon
  • 213
Re: Optimization: GPU-based Submodel Transforms
Nowhere, it just contains changed code base on some revision of the FSO trunk. It's meant for coders only.

 

Offline Bobboau

  • Just a MODern kinda guy
    Just MODerately cool
    And MODest too
  • 213
Re: Optimization: GPU-based Submodel Transforms
ohhhh, nice! I'm assuming you basically used a similar technique that is used for skeletal deformation?

with this in place model instancing becomes a lot easier.
Bobboau, bringing you products that work... in theory
learn to use PCS
creator of the ProXimus Procedural Texture and Effect Generator
My latest build of PCS2, get it while it's hot!
PCS 2.0.3


DEUTERONOMY 22:11
Thou shalt not wear a garment of diverse sorts, [as] of woollen and linen together

 

Offline Swifty

  • 210
  • I reject your fantasy & substitute my own
Re: Optimization: GPU-based Submodel Transforms
Yup, that's pretty much it. :D

As for model instancing, perhaps it's feasible but I've given it cursory thought for now. Right now I have rotation and position info stored in a floating point texture per ship which is then bound in a texture unit before draw. Not very scalable for instanced drawing. Perhaps I could have a transformation texture per ship class which will store the data that the shader can rely on when getting per instance data. Or I can use array textures.

I'll think about it fully when this gets stable.

 

Offline Spoon

  • 212
  • ヾ(´︶`♡)ノ
Re: Optimization: GPU-based Submodel Transforms
Swifty is super cool
Urutorahappī!!

[02:42] <@Axem> spoon somethings wrong
[02:42] <@Axem> critically wrong
[02:42] <@Axem> im happy with these missions now
[02:44] <@Axem> well
[02:44] <@Axem> with 2 of them

  

Offline Bobboau

  • Just a MODern kinda guy
    Just MODerately cool
    And MODest too
  • 213
Re: Optimization: GPU-based Submodel Transforms
Yup, that's pretty much it. :D

As for model instancing, perhaps it's feasible but I've given it cursory thought for now. Right now I have rotation and position info stored in a floating point texture per ship

is this a 1D texture? can it be made into a 1D texture, if so then you can use the second dimension for more than one ship. or make a 3d texture.
and you wouldn't even need to do this per class, you could just put everything into one texture, use the ship class index as the offset in one dimension.
Bobboau, bringing you products that work... in theory
learn to use PCS
creator of the ProXimus Procedural Texture and Effect Generator
My latest build of PCS2, get it while it's hot!
PCS 2.0.3


DEUTERONOMY 22:11
Thou shalt not wear a garment of diverse sorts, [as] of woollen and linen together