I would second @llarian 's need for a step-by-step guide to setup Visual Studio or Studio Code (most preferred) for Orbiter, especially with runtime, all my previous attempts from scratch failed and I had always to re-use a past config from another module... which is far from optimal.
In the...
Scenario included: Nex'Orbiter > Approaching Phebus'
... not yet painted, no parking selection, no lights, not vessel specific, not controlled, feedback welcome... then, more to come...
Instead of "editing" your addon, go to "Post an update" button (grey button, still top right). There you should be able to upload a new version.
Later, in your Addon's "History" tab, you can also delete outdated downloads.
Sorry to report an error while exporting from Blender 4.0 with your 2.1.7 version. I can PM you my file if it helps (I've got a somewhat-large collection hierarchy).
Context =>
Now I want to re-install v2.1.4 in Blender (after removing Addon v2.1.7 from User Preferences panel) and I can't...
Golden rule is to keep meaningful names. In my case, I duplicate with a Blender python script several objects 36 times, so that I end up with a lot of .0xx indices, they all "mean" something and I can't change them manually in Blender... Nevertheless, I can fix in C++ easily but it needs to be...
hi, small bug + easy fix: you export the objects with their exact same names in the .h (+prefix/suffix possibly). Hence, if an object name contains a dot ".", it turns into a syntax error. It happens whenever I duplicated an object multiple times, e.g.:
const UINT Ceiling.000_id = 0...
That's great!
In the "Edit addon" page of your Addon (top-right menu in the "..."), you've got a text field: "Software License", just before "Supported Orbiter Version". I think it is enough. (if you've got a readme file, just repeat it there, then it's attached with the Addon. But if not, just...
I mean for instance "MIT license" (like Orbiter 2016) so we can re-use it further. I would also be able & happy to include it in OMX as a baseline addition. If you integrate this in Orbiter development, it must be MIT (I guess).
oh yes :) for Venus, Ceres and Vesta, please, although for Venus the terrain should be implemented otherwise it's not worth having the map:
https://astrogeology.usgs.gov/search/map/Venus/Magellan/RadarProperties/Venus_Magellan_Topography_Global_4641m_v02
please, aslo, mention the license
is MSVC related to the runtime? I've been facing the problem of not having the runtime recognized, hence the user needs to have VS(2019) installed (which is a pitty for non-dev users). Am I missing some setup at compilation stage?
Don't forget to check the box Parameters > Perturbations > Nonspherical gravity sources
(because Sun-synchronous orbits are permitted by the fact that Mars, like Earth, is not spherical)
Small information, good news:
my sponsor (i.e. my employer...) just renewed its support and confidence in Nex'Orbiter experiment. We'll open the website in a few weeks to tell just-a-little-more about the gameplay, that you could also influence with contributions... In the meantime, let's...
It would be of course nice to use Orbiter for your work. Nevertheless, you can also use another free visualization tool, that makes use of Celestia as a graphic engine: VTS by the French space agency CNES, that also has a stream feature (to display on the fly...). All data need to be formatted...
Hi, I think there is a confusion here:
MJD is just a format, TDB is a time system. SPICE uses a reliable conversion between common time systems (TDB, UTC, TT...) whereas UTC is the time system apparently used by Orbiter. I know it sounds weird but Earth time system (UTC = Orbiter) is quiet...