New bugfix release 1.6.2-beta1
-
Topic authoronetwothree
- Site Admin
- Posts: 706
- Joined: 22.09.2018
- With us: 6 years 1 month
It seems Celestia 1.6.2 cannot overwrite (or use) the old APPDATA/Roaming cel file. Also after the first bookmark the APPDATA bookmark file won't update any longer, but in the Program Files folder favorites.cel is getting updated (but it is obviously not enough).
Last edited by john71 on 23.10.2019, 17:36, edited 2 times in total.
A question before I delve any further into the guts of things.
Is the use of profiles hardcoded now?
I ask because I do not use them, and have nothing in them I can put elsewhere.
I have everything that I can put into full portable mode, thus I can have copies with each configured for different jobs.
If it is hardcoded, then it is just another thing for me to fix for my own usage.
Wanting to know if I need to go spelunking in the code is all.
Janus.
Is the use of profiles hardcoded now?
I ask because I do not use them, and have nothing in them I can put elsewhere.
I have everything that I can put into full portable mode, thus I can have copies with each configured for different jobs.
If it is hardcoded, then it is just another thing for me to fix for my own usage.
Wanting to know if I need to go spelunking in the code is all.
Janus.
Hi,john71 wrote:Very nice work! Nice fps rates on Windows 10 64 bit, and everything works perfectly.
Only one minor problem: I cannot save any bookmarks.
Celestia 1.6.2 simply forgets the previous bookmarks for some reason when it starts.
Other than that it is truly nice! Thank you for the hard work!
As well said john71, I have same problem.
None favorite (bookmark) !
When I double-click on file 'favorites.cel', i've got this error...
Inside celestia.cfg, i found line ' FavoritesFile "favorites.cel" '
No problem with cel 161.
Soft: Celestia 1.6.2
PC : Intel Core i9-9900K (4 GHz) , Chipset Z390 Exp, RAM 32 Go DDR4 3000 Mhz, SSD M.2 512 Go + HDD 3 To, MSI GeForce RTX 2080 8Go - W10 64b
I lost my old user, so with us: since more 12 years
=> It is by doubting everything that everybody approaches the truth !
PC : Intel Core i9-9900K (4 GHz) , Chipset Z390 Exp, RAM 32 Go DDR4 3000 Mhz, SSD M.2 512 Go + HDD 3 To, MSI GeForce RTX 2080 8Go - W10 64b
I lost my old user, so with us: since more 12 years
=> It is by doubting everything that everybody approaches the truth !
-
Topic authoronetwothree
- Site Admin
- Posts: 706
- Joined: 22.09.2018
- With us: 6 years 1 month
john71 wrote:It seems Celestia 1.6.2 cannot overwrite (or use) the old APPDATA/Roaming cel file. Also after the first bookmark the APPDATA bookmark file won't update any longer, but in the Program Files folder favorites.cel is getting updated (but it is obviously not enough).
weird
Janus wrote:Is the use of profiles hardcoded now?
Yes, but maybe i'll add a compile time switch for portable builds.
john71 wrote:Why do we need a cel file in the APPDATA folder? Why can't Celestia use the cel file in the Program Files folder?
Because it's not 1995.
@onetwothree
A compile time switch for portable would be appreciated.
It would save me some work eliminating appdata & registry calls.
I always force everything I can to use config files, json files, or if nothing else works, xml files.
Other than the OS and a few things that are hardcoded to it, nothing goes on C.
I also run Celestia, and everything else as Administrator.
So please, add that compile time switch.
I at least would greatly appreciate it.
Janus.
A compile time switch for portable would be appreciated.
It would save me some work eliminating appdata & registry calls.
I always force everything I can to use config files, json files, or if nothing else works, xml files.
Other than the OS and a few things that are hardcoded to it, nothing goes on C.
I also run Celestia, and everything else as Administrator.
So please, add that compile time switch.
I at least would greatly appreciate it.
Janus.
-
Topic authoronetwothree
- Site Admin
- Posts: 706
- Joined: 22.09.2018
- With us: 6 years 1 month
-
Topic authoronetwothree
- Site Admin
- Posts: 706
- Joined: 22.09.2018
- With us: 6 years 1 month
-
- Developer
- Posts: 234
- Joined: 05.01.2018
- Age: 38
- With us: 6 years 10 months
- Location: Wrocław
- Contact:
john71 wrote:Celestia 1.6.2 starts very slowly at the first time after booting Windows. The second, third etc. times have no problems.
Looks like you just have slow storage drive. Did you run 1.6.1 on the same machine?
Still formally developer, but too tired to develop. I feel sad, but Celestia is going forward despite it.
Btw, the universe is ruled by electricity.
Btw, the universe is ruled by electricity.
I don't think so. I have a new SSD c:/ drive and an 8 core processor with 16GB RAM. I suspect it is some kind of antivirus or security procedure, which slows the program down the first time it is launched AFTER BOOTING. After the first run it starts nicely again at the second, third etc. times until the next boot.
Added after 1 minute 21 seconds:
Added after 2 minutes 3 seconds:
By the way, you made EXCELLENT progress in the last few months. Do not despair.
Added after 1 minute 21 seconds:
onetwothree wrote:80% market share and 0 (zero) Celestia developers.
Added after 2 minutes 3 seconds:
By the way, you made EXCELLENT progress in the last few months. Do not despair.
Last edited by john71 on 01.11.2019, 14:59, edited 1 time in total.
Markerz wrote:Since Celestia is now a sandboxed application, modification to the data folder inside the application bundle is disallowed (for example, adding additional plugins, textures), instead one should resort to the option "Change Configuration File" in the Celestia menu in menubar to change the path of celestia.cfg and data directory that Celestia will attempt to load. Extra files, scripts will be read from the sandboxed path, which should be ~/Library/Containers/space.celestia.Celestia/Data/Library/Application Support/CelestiaResources
May I ask why this is a change? As Celestia 1.6.1 and previous versions do not disallow modification inside the app bundle.
-
- Developer
- Posts: 274
- Joined: 29.01.2009
- Age: 29
- With us: 15 years 9 months
- Location: Suzhou, China
LukeCEL wrote:Markerz wrote:Since Celestia is now a sandboxed application, modification to the data folder inside the application bundle is disallowed (for example, adding additional plugins, textures), instead one should resort to the option "Change Configuration File" in the Celestia menu in menubar to change the path of celestia.cfg and data directory that Celestia will attempt to load. Extra files, scripts will be read from the sandboxed path, which should be ~/Library/Containers/space.celestia.Celestia/Data/Library/Application Support/CelestiaResources
May I ask why this is a change? As Celestia 1.6.1 and previous versions do not disallow modification inside the app bundle.
Sorry its a late reply, i've been busy recently and i forgot to address this.
Modification inside the app bundle is still possible and actually not disallowed in this version, contrary to what i said in that post(I'll update it later).
Apple requires all application to be codesigned starting from a point in time. Celestia 1.6.1 is developed before that so it does not need to be codesigned. Codesigning is basically used to protect your app being modified, because the app will fail the verification and refuse to run (displaying an alert saying the app is corrupt) if a codesigned app is modified.
this led me to the conclusion that the app bundle can't be modified at all. but actually, codesigning can be applied to only some of the files of the application bundle. Celestia 1.6.2 beta1 did not codesign the 'CelestiaResouces' folder, you should still be able to modify this folder and run it.
Thanks for the reply!
Oh good, this is the main thing I was worried about. If modifying the 'CelestiaResources' folder became forbidden, then add-on installation would become a lot more complicated.
Markerz wrote:Celestia 1.6.2 beta1 did not codesign the 'CelestiaResouces' folder, you should still be able to modify this folder and run it.
Oh good, this is the main thing I was worried about. If modifying the 'CelestiaResources' folder became forbidden, then add-on installation would become a lot more complicated.