Vincent,
This is a known bug which Chris posted about.
See viewtopic.php?f=3&t=13376&p=111543&hilit=red+ecliptic#p111543
Bugs in 1.6.0
Re: Bugs in 1.6.0
Selden
-
- Developer
- Posts: 1356
- Joined: 07.01.2005
- With us: 19 years 10 months
- Location: Nancy, France
Re: Bugs in 1.6.0
OK.selden wrote:This is a known bug which Chris posted about.
See viewtopic.php?f=3&t=13376&p=111543&hilit=red+ecliptic#p111543
However, I can't reproduce this bug on my system, that's why I was wondering
whether the ecliptic line showed up by default or after running a script...
Anyway, I'll add the ecliptic line checkbox to the Windows GUI in 1.6.1:
@+
Vincent
Celestia Qt4 SVN / Celestia 1.6.1 + Lua Edu Tools v1.2
GeForce 8600 GT 1024MB / AMD Athlon 64 Dual Core / 4Go DDR2 / XP SP3
Vincent
Celestia Qt4 SVN / Celestia 1.6.1 + Lua Edu Tools v1.2
GeForce 8600 GT 1024MB / AMD Athlon 64 Dual Core / 4Go DDR2 / XP SP3
Re: Bugs in 1.6.0
I supose that i can expose my problem here:
In versioncelestia 1.60
Some items disappear when one is seen close
here an example with screnshots
here the canadarm is visible but if i change a little the view...
ON 1.50 final everything is right .The result is the same with dds texture or jpg
Linuxman
In versioncelestia 1.60
Some items disappear when one is seen close
here an example with screnshots
here the canadarm is visible but if i change a little the view...
ON 1.50 final everything is right .The result is the same with dds texture or jpg
Linuxman
StarWarSaga 2001 odyssey Back in USSR by linuxman
http://celestiasws.free.fr
AMD-64x2-6000 4 gb DDR2-800 geforce GTX460 1gb Asus M2N-sli-d Apple cinema display 23" Linux Gentoo 64 bits Vista pro 64 bits celestia 1.60 official
http://celestiasws.free.fr
AMD-64x2-6000 4 gb DDR2-800 geforce GTX460 1gb Asus M2N-sli-d Apple cinema display 23" Linux Gentoo 64 bits Vista pro 64 bits celestia 1.60 official
Re: Bugs in 1.6.0
Linuxman.
Are you using the new NormalizeMesh and MeshScale?
If so, you may have set Radius too small.
Are you using the new NormalizeMesh and MeshScale?
If so, you may have set Radius too small.
Selden
Re: Bugs in 1.6.0
Thank you Selden, i don't use "NormalizeMesh and MeshScale"
I will do some test and inform you.
inuxman
I will do some test and inform you.
inuxman
StarWarSaga 2001 odyssey Back in USSR by linuxman
http://celestiasws.free.fr
AMD-64x2-6000 4 gb DDR2-800 geforce GTX460 1gb Asus M2N-sli-d Apple cinema display 23" Linux Gentoo 64 bits Vista pro 64 bits celestia 1.60 official
http://celestiasws.free.fr
AMD-64x2-6000 4 gb DDR2-800 geforce GTX460 1gb Asus M2N-sli-d Apple cinema display 23" Linux Gentoo 64 bits Vista pro 64 bits celestia 1.60 official
- Chuft-Captain
- Posts: 1779
- Joined: 18.12.2005
- With us: 18 years 11 months
Re: Bugs in 1.6.0
Linuxman,
I have sometimes seen a problem when using Normalizemesh/MeshScale in circumstances where the scaled radius effectively exceeds the SSC specified radius (ie. the mesh is not completely inside the bounding sphere.) Parts of the mesh outside the bounding sphere will be "chopped off".
I think that this is the problem that Selden's referring to. If you DO use Normalizemesh/MeshScale then you may experience this problem.
However, I don't think this is the problem you are experiencing. You say that you are NOT using Normalizemesh/MeshScale, so there must be another explanation.
Are there any transparent/translucent textures involved with any of the meshes? These sometimes can cause depth-sorting problems.
I suspect that you are using a number of separate meshes in this scene. I have struggled with problems like this when multiple meshes (not using Normalizemesh) are in close proximity to each other and their bounding spheres overlap.
This I think is most likely to be the actual source of your problem.
When bounding spheres are in close proximity and overlap, Celestia can become confused about which object is closer to the observer, and will sometimes (depending on viewpoint) decide not to display one or other of the objects (thinking it is hidden by the other object I guess).
I have noticed this problem become worse in 1.6.0.
CC
I have sometimes seen a problem when using Normalizemesh/MeshScale in circumstances where the scaled radius effectively exceeds the SSC specified radius (ie. the mesh is not completely inside the bounding sphere.) Parts of the mesh outside the bounding sphere will be "chopped off".
I think that this is the problem that Selden's referring to. If you DO use Normalizemesh/MeshScale then you may experience this problem.
However, I don't think this is the problem you are experiencing. You say that you are NOT using Normalizemesh/MeshScale, so there must be another explanation.
Are there any transparent/translucent textures involved with any of the meshes? These sometimes can cause depth-sorting problems.
I suspect that you are using a number of separate meshes in this scene. I have struggled with problems like this when multiple meshes (not using Normalizemesh) are in close proximity to each other and their bounding spheres overlap.
This I think is most likely to be the actual source of your problem.
When bounding spheres are in close proximity and overlap, Celestia can become confused about which object is closer to the observer, and will sometimes (depending on viewpoint) decide not to display one or other of the objects (thinking it is hidden by the other object I guess).
I have noticed this problem become worse in 1.6.0.
CC
"Is a planetary surface the right place for an expanding technological civilization?"
-- Gerard K. O'Neill (1969)
CATALOG SYNTAX HIGHLIGHTING TOOLS LAGRANGE POINTS
-- Gerard K. O'Neill (1969)
CATALOG SYNTAX HIGHLIGHTING TOOLS LAGRANGE POINTS