Accurate star sizes

Description: The place to discuss creating, porting and modifying Celestia's source code.

Joey P.
Topic author
Avatar
Joey P.
Topic author
Posts: 11
With us: 24 days 10 hours

#1by Joey P. » 12.11.2017, 02:04

Could someone please provide an addon/.stc where Antares, Betelgeuse, the Ruby Star (=119 Tau), P Cygni, R Lep, T Cephei (=HIP 104451) and Rho Cassiopeiae have their radii modified to correction? I have tried to make my own addon/.stc file but it would not work.

Antares: 883 solar radii (https://simple.wikipedia.org/wiki/Antares)
Betelgeuse: anywhere between 887 + 203 to 1,180 solar radii (https://simple.wikipedia.org/wiki/Betelgeuse, https://en.wikipedia.org/wiki/Betelgeuse)
The Ruby Star: 608 solar radii (http://www.newforestobservatory.com/2012/07/02/th ... in-the-sky-119-tauri-ce-tauri/)
P Cygni: 77 solar radii (https://jumk.de/astronomie/big-stars/p-cygni.shtml)
R Lep: 500 solar radii
T Cephei: 540 solar radii (http://vizier.u-strasbg.fr/viz-bin/VizieR-5?-out. ... ource=II/224/cadars&recno=9837)
Rho Cassiopeiae: 450 solar radii (https://jumk.de/astronomie/big-stars/rho-cassiopeiae.shtml)

Thank you. - Joey P.

selden
Avatar
selden
Posts: 10117
With us: 15 years 2 months
Location: NY, USA

#2by selden » 12.11.2017, 13:32

What format did you use for your .stc catalog?
If you can provide an example, someone might be able to point out your mistakes.

The file /data/charm2.stc includes updated radii for many stars, thus providing valid examples of how to change them. As another example, here's an stc which changes the radius of Antares.

Code: Select all

Modify 80763 { Radius 614303100 }
Selden

John Van Vliet
Avatar
John Van Vliet
Posts: 2662
With us: 15 years 2 months

#3by John Van Vliet » 13.11.2017, 06:11

also i hope you are NOT using Microsoft word to do this

it will not work

use SciTe or the scite based editor "notepad++"

http://www.scintilla.org/

https://notepad-plus-plus.org/

then there is always Emacs ( there is a windows build )
-- one of the BEST in the world --
https://www.gnu.org/software/emacs/

Janus
Janus
Posts: 105
With us: 1 year 3 months

#4by Janus » 13.11.2017, 08:09

An extra note to be careful of.

You also need to be sure your editor is in Ansi/Ascii mode, not utf-8 because the parser in Celestia has issues with MBCS in ini/cfg/ssc/sst/data files.

Notepad++ defaults to UTF-8 on import unless you set it otherwise because it is internationalization friendly that way.
I changed the source of mine and recompiled to force it Ansi/Ascii unless I select otherwise.

Just don't want to see anyone else get stuck in the same rabbit hole I did.
You can easily check for out of bounds characters using ztree viewing in hex mode.
The quickest check is to look for characters with values $80(0x80) and above.


Janus.

Joey P.
Topic author
Avatar
Joey P.
Topic author
Posts: 11
With us: 24 days 10 hours

#5by Joey P. » 15.11.2017, 04:33



Return to “Development”

Who is online (over the past 5 minutes)

Users browsing this forum: 2 guests