SF models here
-
Topic authorCham
- Posts: 4324
- Joined: 14.01.2004
- Age: 60
- With us: 20 years 8 months
- Location: Montreal
SF models here
I was experimenting a lot with the new specular reflection code (CVS 1.5.0), and I've edited many models (real spacecraft and SF models too). I'll publish some of the SF models here, starting with this one (real spacecraft are presented in another thread) :
If you want, you can download the model from the link below (the SSC is temporary and used only to show the model with its glowing lights). Enjoy !
http://nho.ohn.free.fr/celestia/Cham/Enterprise.zip (508 KB zip file)
If you want, you can download the model from the link below (the SSC is temporary and used only to show the model with its glowing lights). Enjoy !
http://nho.ohn.free.fr/celestia/Cham/Enterprise.zip (508 KB zip file)
"Well! I've often seen a cat without a grin", thought Alice; "but a grin without a cat! It's the most curious thing I ever saw in all my life!"
-
Topic authorCham
- Posts: 4324
- Joined: 14.01.2004
- Age: 60
- With us: 20 years 8 months
- Location: Montreal
Here's another one :
Enjoy !
http://nho.ohn.free.fr/celestia/Cham/Vador.zip (1.2 MB zip file)
EDIT : I forgot to edit the SSC. You probably don't have the planets around Altair, so just use your favorite SSC ...
O well, and I forgot to say those models should be used with Celestia CVS (aka 1.5.0), to enjoy the new specular reflections.
Enjoy !
http://nho.ohn.free.fr/celestia/Cham/Vador.zip (1.2 MB zip file)
EDIT : I forgot to edit the SSC. You probably don't have the planets around Altair, so just use your favorite SSC ...
O well, and I forgot to say those models should be used with Celestia CVS (aka 1.5.0), to enjoy the new specular reflections.
"Well! I've often seen a cat without a grin", thought Alice; "but a grin without a cat! It's the most curious thing I ever saw in all my life!"
-
- Developer
- Posts: 3776
- Joined: 04.02.2005
- With us: 19 years 8 months
-
Topic authorCham
- Posts: 4324
- Joined: 14.01.2004
- Age: 60
- With us: 20 years 8 months
- Location: Montreal
chris wrote:Is that emissive texture or material on the Enterprise model? Nice to see that feature getting some use. It's especially useful when a spacecraft slips into the shadow of a planet.
--Chris
Actually, it's Jestr's trick. The model was separated into two parts, one for the lights with an emissive command in the SSC. I want to use the new code features, but currently I'm unable to make them to work.
Chris, could you explain what we are supposed to do in the modeler, so Celestia could recognise the emissive textures/material ? And what about the normalMap ? I wasn't able to use that yet.
"Well! I've often seen a cat without a grin", thought Alice; "but a grin without a cat! It's the most curious thing I ever saw in all my life!"
-
- Posts: 835
- Joined: 27.09.2004
- With us: 20 years
- Location: Massachusetts, USA
-
- Posts: 23
- Joined: 22.10.2005
- With us: 18 years 11 months
- Location: Missouri
Cham wrote:Chris, could you explain what we are supposed to do in the modeler, so Celestia could recognise the emissive textures/material ? And what about the normalMap ? I wasn't able to use that yet.
Well, I'm not Chris, and I don't use NormalMaps, but I got emissive to work in a model.
If you don't need an emissive texture map, you just have to add the emissive color declaration to the appropriate material definition. This is what was emitted by my Anim8or cmod export script for the "glass" windows in the picture above. (I'm still working on it.)
Code: Select all
material # 58
# diffuse 0.788 0.957 0.98
# diffusepower 1 # Kd
diffuse 0.788 0.957 0.98
opacity 0.8
specular 0.576 0.576 0.576
# specularpower 0.8 # Ks
specpower 204 # Ks*255
# emissive 0.992 0.945 0.627
# emissivepower 0.5 # Ke
emissive 0.496 0.473 0.314 # product
end_material
Selden
- cartrite
- Posts: 1978
- Joined: 15.09.2005
- With us: 19 years
- Location: Pocono Mountains, Pennsylvania, USA Greate Grandfother from Irshava, Zakarpattia Oblast Ukraine
Cham wrote:
I'm not Chris either, but tangents must be generated for the model. cmodfix -t a.cmod b.cmod. I'm not sure how to generate them for 3ds model though.
And what about the normalMap ? I wasn't able to use that yet.
I'm not Chris either, but tangents must be generated for the model. cmodfix -t a.cmod b.cmod. I'm not sure how to generate them for 3ds model though.
VivoBook_ASUSLaptop X712JA_S712JA Intel(R) UHD Graphics 8gb ram. Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz, 1190 Mhz, 4 Core(s), 8 Logical Processor(s) 8 GB ram. Running on Windows 11 and OpenSuse 15.4
I'm working on it! I'm working on it!
Patience!
Pictures of some of my earlier work on the model are on the Web at http://www.lepp.cornell.edu/~seb/celest ... index.html
My primary emphasis at the moment is to try to reduce the resources it requires. It's running at only 15 fps on my home system (3.4GHz P4 + GF6600GT) and half that on the system at work (2.4GHz P4 + FX5200).
I've got some more meshes that can be optimized, but I fear a large part of the problem is that it consists of a dozen separate models. Pieces will get left behind during the expedition to Mars.
Patience!
Pictures of some of my earlier work on the model are on the Web at http://www.lepp.cornell.edu/~seb/celest ... index.html
My primary emphasis at the moment is to try to reduce the resources it requires. It's running at only 15 fps on my home system (3.4GHz P4 + GF6600GT) and half that on the system at work (2.4GHz P4 + FX5200).
I've got some more meshes that can be optimized, but I fear a large part of the problem is that it consists of a dozen separate models. Pieces will get left behind during the expedition to Mars.
Selden
-
- Site Admin
- Posts: 4211
- Joined: 28.01.2002
- With us: 22 years 8 months
- Location: Seattle, Washington, USA
selden wrote:I'm working on it! I'm working on it!
Patience!
Pictures of some of my earlier work on the model are on the Web at http://www.lepp.cornell.edu/~seb/celest ... index.html
My primary emphasis at the moment is to try to reduce the resources it requires. It's running at only 15 fps on my home system (3.4GHz P4 + GF6600GT) and half that on the system at work (2.4GHz P4 + FX5200).
I've got some more meshes that can be optimized, but I fear a large part of the problem is that it consists of a dozen separate models. Pieces will get left behind during the expedition to Mars.
The fact that there are twelve separate models shouldn't cause any problems (especially not in the current CVS version.) How many triangles are in the model? Does it run substantially faster in one of the non-OGL2 render paths? I know that there can be some slowdown when using a lot of materials. An option to condense identical material definitions to a single material would be a very useful feature for cmodfix.
--Chris
Chris,
The largest model has about 300 meshes, so there are about 300 material definitions. Merging all the meshes into a single mesh reduces it to 14 materials, so eliminating duplicates would help a lot. Unfortunately, I can't merge all the meshes until Anim8or's export surface normal problem is fixed in the next beta. At the moment I need to use cmodfix to regenerate the normals, but it can't handle more than one material per mesh.
There seems to be about a 40% speedup when using the Basic render path compared to using the OGL2 render path with an FX5200 graphics card.
At one time I thought I had it up to 60fps on my home system, but I haven't been able to reproduce it. Maybe that was in the Basic path, I'm not sure.
Dollan,
Don't forget that the 10-meter version of Orion is only good for interplanetary travel at relatively slow speeds. Its isp is only about 1800. A much larger plate is needed in order to get the isp values up to where external plasma pulse drives can almost be used for interstellar travel.
The largest model has about 300 meshes, so there are about 300 material definitions. Merging all the meshes into a single mesh reduces it to 14 materials, so eliminating duplicates would help a lot. Unfortunately, I can't merge all the meshes until Anim8or's export surface normal problem is fixed in the next beta. At the moment I need to use cmodfix to regenerate the normals, but it can't handle more than one material per mesh.
There seems to be about a 40% speedup when using the Basic render path compared to using the OGL2 render path with an FX5200 graphics card.
At one time I thought I had it up to 60fps on my home system, but I haven't been able to reproduce it. Maybe that was in the Basic path, I'm not sure.
Dollan,
Don't forget that the 10-meter version of Orion is only good for interplanetary travel at relatively slow speeds. Its isp is only about 1800. A much larger plate is needed in order to get the isp values up to where external plasma pulse drives can almost be used for interstellar travel.
Selden
-
- Developer
- Posts: 3776
- Joined: 04.02.2005
- With us: 19 years 8 months
selden wrote:...My primary emphasis at the moment is to try to reduce the resources it requires. It's running at only 15 fps on my home system (3.4GHz P4 + GF6600GT) and half that on the system at work (2.4GHz P4 + FX5200).
I've got some more meshes that can be optimized, but I fear a large part of the problem is that it consists of a dozen separate models. Pieces will get left behind during the expedition to Mars.
How many poly do you have actually?
ElChristou,
They aren't all that bad, I think. The largest model has
They aren't all that bad, I think. The largest model has
Code: Select all
# 284 materials (+ 0 unused); 106608 vertices, 128629 triangles
# 259 Shapes (+ 25 with no vertices; max: 6128, avg: 411,
# max Triangles/Shape: 5424, avg: 496)
Selden
-
- Developer
- Posts: 3776
- Joined: 04.02.2005
- With us: 19 years 8 months
-
- Site Admin
- Posts: 4211
- Joined: 28.01.2002
- With us: 22 years 8 months
- Location: Seattle, Washington, USA
selden wrote:Chris,
The largest model has about 300 meshes, so there are about 300 material definitions. Merging all the meshes into a single mesh reduces it to 14 materials, so eliminating duplicates would help a lot. Unfortunately, I can't merge all the meshes until Anim8or's export surface normal problem is fixed in the next beta. At the moment I need to use cmodfix to regenerate the normals, but it can't handle more than one material per mesh.
There seems to be about a 40% speedup when using the Basic render path compared to using the OGL2 render path with an FX5200 graphics card.
At one time I thought I had it up to 60fps on my home system, but I haven't been able to reproduce it. Maybe that was in the Basic path, I'm not sure.
The 6600 should be able to handle the triangle count, but I'm not surprised that the 5200 slows down with such a large amount of geometry.
If the 6600 can display the model at 60fps without OpenGL 2.0, that would support my theory that the overhead of switching materials is to blame. That would actually be a good thing, because uniquifying materials is easy to do. It could even be performed with a relatively low cost at model load time in Celestia so that even existing models could benefit.
--Chris