Search results

Hence, the dust, okay. 1MPH = 1.6km/h = 45cm/s (y)

quiet brutal touchdown, IMHO. Total flight = 10min, including a 2- or 3-min weightless flight maximum............ the landing of the booster is impressive.

The problem is about the shadows (whatever the shadowing object) onto custom objects (onto pre-defined objects like BLOCK seems ok, as one can see from your tests). As illustrated by @Buck Rogers above, actually.

I made a major fix for the server's security (that was harassed by bots...). Then you must use the v1.1.1 version above. The server on orbiterx.obspm.fr:1515 was restarted. See Addon's presentation to see the new features. Hope you'll like them. (this is still not the /NET 6 upgrade, which is...

Boxx updated Nex'Orbiter with OMX with a new update entry: v1.1.1 Read the rest of this update entry...

still minor bugs that I could not fix right now: 1) at startup: connect => (it seems to be locked) => disconnect > reconnect... then, demo is launched => exit => connect again. Should solve the issue for future connections. 2) if disconnected or CTD and you try to reconnect, nothing happens...

Regarding the shadows, I just reported an issue with @LordCroussette's Lunar bases. But I see the same problem here: The shadows are not drawn on the Delta Glider, or any surface but the ground... weird! is there a special computation of the received shadows for the "ground" and not for any...

Suggestion : you could put your large textures, that are common to multiple stations in one single upper subfolder in <orbiter>/Textures (e.g. spaceblanket_gold 16MB) and call them from there in the .msh files... I'm trying this right now... and will keep you informed edit: not worth doing (as...

also, small bug with the shadows (graphic engine bug?) : the shadows of the flags don't extend on the domes ... not disturbing so much, before noticing it!

Hi, your textures are only compatible with Orbiter_NG, D3D9. Textures appear "pure white" in orbiter.exe. Is there a possible small fix to replace "pure white" textures with some backup textures? Or ideally to translate all textures in non-D3D9 compatible formats as well.

Hi, indeed that's an important topic to learn/teach how to compile. But do I miss something here?... if the point is not to get rid of VS Community, why going to CMake and not just compile with VS Community?! I'm very interested to use CMake without VS Community for Orbiter's addon or Orbiter...

@LordCroussette : excellent development line, all these bases, keep going please!! May I suggest: Pad numbers should be reversed, as the intuitive spacecraft pointing should be "to" the taxiway, not "from" it, for a commuter to pick up the visitors from the docking port (or they should walk to...

Thank you for sharing your ideas. I think the design should be matured further before modeling anything seriously. The community here may be willing to suggest technical performances like thrust, Isp that seem to me very low for space flight (but I'm not specialist).

then, maybe an idea for me in a future addon... (after my work on Phebus' wheel station, maybe). Starting from an existing van, I think I could code an automated commuter when a glider has landed......... BTW: wiki for Rupes Recta

niiiiiice ! :) have you considered a pressurized van to dock to Orbiter and commute to a building entry?

can you show/PM the drawings?

Nice to know, thank you! I was hoping that some I.A.-engine could have filled the gaps, based on the known parts and extrapolating somehow... but no, still a thorough manual editing, though. Impressive, then.

Hi, can you elaborate on the "fictional" parts? i.e. how You or Astra extrapolated colors and non-imaged parts... In anyway, I think it's a good idea to get inspired by Celestia addon developers.

Some progress... still a bug due to the migration to .NET6: The current commit in the "Limit-to-server" branch is a .NET6 migrated version of OMX ServerConsole.exe that can build and run (with build settings in VSCode style, see .vscode subfolder to adapt path in the .json to your own install...

OMX (the multi-player engine) is a fork of OMP in GPL v2. Hence, it will remain open-source, indeed. Yes, it must be! In Nex'Orbiter, the wheel station is delivered and automatically assembled in LEO. If we want an outpost to rest at 1G before flying further, we need multiple pilots and a good...