Project "Celestia Origin", release dated April 30, 2021
-
- Posts: 202
- Joined: 21.10.2021
- Age: 16
- With us: 3 years 1 month
- Location: Novo Hamburgo, State of Rio Grande do Sul, Brazil
- trappistplanets
- Posts: 639
- Joined: 11.06.2020
- Age: 17
- With us: 4 years 5 months
-
Topic authorArt Blos
- Moderator
- Posts: 1150
- Joined: 31.08.2017
- Age: 32
- With us: 7 years 2 months
- Location: Volgodonsk, Rostov Oblast, Russia
I converted all the light curve models using everywhere the same algorithm. If there is some problem with the models or with the video card, then all such models would not work, and not just the above 93 asteroids.gironde wrote:Here is a screenshot with celestia-log edited and in the center the asteroid 94 Aurora using 94_aurora.cmod
When I use asteroid-large.cmod I can see Aurora well.
Is this the same issue as I encountered with DaveBowman2001's Starlink cmod? (an 'obj to cmod' conversion not fully compatible on all graphics cards)
Founder and head of the project "Celestia Origin"
-
Topic authorArt Blos
- Moderator
- Posts: 1150
- Joined: 31.08.2017
- Age: 32
- With us: 7 years 2 months
- Location: Volgodonsk, Rostov Oblast, Russia
No answer. I have not come across this. Everything worked on different systems (I'm on Windows 11 now). Have someone else test the above models.gironde wrote:I didn't say they were the only ones. Those from n ° 2 to n ° 19 work correctly and for the moment I have not tested beyond n ° 94.
What is amazing is that I installed your models from the April 30 edition and did not notice any malfunction. So is this a windows 10 update that would have made them impossible to read in celestia because I repeat they are correctly opened in cmodview?
Founder and head of the project "Celestia Origin"
- gironde
- Posts: 851
- Joined: 16.12.2016
- Age: 72
- With us: 7 years 11 months
- Location: Montigny-Les-Metz, France
It's bad !I wrote
I found where the problem comes from
oddly, a file called for example 256_walpurga.cmod must be loaded by Mesh "256 walpurga.cmod".
A space replaces the underscore (_)
And in this case the file is found and loaded
I come to do my 'mea culpa' because I got confused with this .cmod story
I have a particular build of celestia so that I can use Celestia 1.6.1 and 1.6.2.2 with the same files without having to repeat them. It works by building the 2 celestia.cfg for this purpose. But some files like basic 'models' and 'textures' (in the root of celestia) are not 'exportable' in celestia.cfg. And with time I forgot it; So I tried to correct some errors in a file that Celestia never called.
So there you have it, Celestia Origin's .cmod files are correct, the '_' character is recognized and the name used in Mesh must be the same as that of the 'models' folder.
I apologize to Art Blos for worrying him for no reason.
Added after 1 hour 32 minutes:
In LUT5, in the renderBox.lua module the following instructions are extra and are useless. They were probably trials and stayed in the final version:
lines 88 to 91
Code: Select all
starStyleLeftOffset = guideLeftOffset - 2
starStyleUpOffset = 9 + 20 * (nguide + 2)
textureResLeftOffset = guideLeftOffset - 2
textureResUpOffset = 9 + 20 * (nguide + 3)
in config.lua the table renderclass is not adequate :
Code: Select all
renderclass =
{
"", -- Group Separation Mark
"Constellations",
"Galaxies",
"Globulars",
"Open Clusters",
"Nebulae",
"Stars",
"Planets",
"",-- "9", --"Planets",
"",-- "10", --"Dwarf Planets",
"",-- "11", --"Moon",
"",-- "12", --"Minor Moon",
"13", --"Asteroid",
"14", --"Comet",
"15", --"Spacecraft",
}
"9", "10", "11", "12" are programmed in the code ('if k == 9 then' ... elseif k == 10 then ... and the following) but not implemented in config.lua
"13, "14", "15" are implemented in config.lua but are not programmed in the code, and instructions are missing
elseif k == 13 then ...
elseif k == 14 then ...
elseif k == 15 then ...
in the choice of Celestia Origin renderclas must be:
Code: Select all
renderclass =
{
"", -- 1 Group Separation Mark
"Constellations", -- 2
"Galaxies", -- 3
"Globulars", -- 4
"Open Clusters", -- 5
"Nebulae", -- 6
"Stars", -- 7
"Planets", -- 8
"",-- "9", --"Planets",
"",-- "10", --"Dwarf Planets",
"",-- "11", --"Moon",
"",-- "12", --"Minor Moon",
"", -- "13" --"Asteroid",
"", -- "14" --"Comet",
"", -- "15" --"Spacecraft",
}
my renderclass withh all is:
Code: Select all
renderClass = -- not move the order -- table of Class of 15 objects
{
"", -- 1 - for label "Constell. in Latin"
"Constellations", -- 2 - constellations
"Galaxies", -- 3 - galaxies
"Globulars", -- 4 - globular clusters
"Open Clusters", -- 5 - open clusters
"Nebulae", -- 6 - nelulae
"Stars", -- 7 - Star
"", -- 8 - in celestia, everything that revolves around the stars "Planets (class)",
"9", -- 9 - AllPlanet
"10", -- 10 - AllDwarfPlanets
"11", -- 11 - AllMoons
"12", -- 12 - AllMinorMoons
"13", -- 13 - AllAsteroids
"14", -- 14 - AllComets
"15", -- 15 - AllSpacecrafts
}
In addition, for functionalities "9" to "15" to be operational, an object table is needed for each.
AllPlanets.lua
AllDwarfplanets.lua
AllMoons.lua
AllMinorMoons.lua
AllAsteroids.lua
AllComets.lua
AllSpacecrafts.lua
my renderBox with all functionalities (in french)
- gironde
- Posts: 851
- Joined: 16.12.2016
- Age: 72
- With us: 7 years 11 months
- Location: Montigny-Les-Metz, France
here you will find my renderBox.lua module as well as my object tables for this module and the settings to modify in config.lua
Remember that when you make modifications in Lua_applications, it is highly preferable to make a backup of your modules before modifications (here tools / renderBox.lua and config.lua)
Remember that when you make modifications in Lua_applications, it is highly preferable to make a backup of your modules before modifications (here tools / renderBox.lua and config.lua)