Search results

Thank you... but actually, maybe it would help ..... Actually I requested a wheel station for some time (the existing one is too limited, hosting a maximum of 2 vessels, nose-to-nose), but nobody seemed interested :cry: so I did it by myself :cool: => already some cool anim and soon more...

I'm now walking this (long) way for C# and .NET... then I think it is an excellent idea to do it for Orbiter 2016 / OpenOrbiter as a whole. I would suggest you to focus on the setup for Studio Code, not for Visual Studio (where we end up with not understanding anything anymore...). I'm...

Ok, this work-package has been started. Actually, C#, .NET and Studio Code (without C# dev kit) have become open source. My point is to set up a build process for Studio Code and .NET in command line, that gets rid of Visual Studio. Thus, I won't include .vs, .vscode, bin/, obj/ in the git repo...

Although the docking is quiet tolerant (closing velocity can be up to 1m/s), a good technique is the standard procedure given in Orbiter's manual: 1) align at the entry of the corridor (x and + targets at center), 2) approach smoothly while keeping both targets (with RCS LIN, then Ctrl+Key), 3)...

29 downloads... did anybody try to dock and find the surprise?

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...

Boxx submitted a new addon: Phebus' Wheel Station - in Nex'Orbiter project Read more about this addon...

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...

4th package... yeah :)

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.

Thank you for the quick fix. Version 2.1.8 works also for me now! Again, excellent Blender addon.

Thank you for these additional maps... let's explore ;)

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

maybe this can help : https://www.researchgate.net/publication/313994327_Using_the_General_Mission_Analysis_Tool_GMAT

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?