Orbiter Screenshot Thread

0003.jpg
I didn't know that the DrawOrbits module displays the orbits of celestial bodies.

@Nikogori, have you thought about writing a short (or detailed) tutorial about your flight using IMFD?
 
Screenshots from the first two launches of my new space station: Sailiniq! (Taken from my livestream, so the quality isn't all great)

The launch of Sailiniq aboard the SLS!
1739031169678.png
Space Shuttle Olympic is visible on LC-39A while the SLS takes off from LC-39B.
1739031231847.png
And Sailiniq is in orbit!
1739031250775.png
About a month later (well a few minutes IRL), Olympic takes off for mission SSM-89, carrying abord the second module of Sailiniq, and a PMA Adapter.
1739031299201.png
The payload bay doors are opened.
1739031314464.png
Olympic has rendez-vous Sailiniq in orbit.
1739031331728.png
Module #2 docked!
1739031344194.png
And Olympic is docked after docking the PMA Adapter first!
1739031360194.png
And, of course, the return to the Kennedy Space Center at the end of the mission.
1739031376836.png
1739031382147.png
 
Another shuttle flight, this time SSM-90 with Brunswicker, bringing a third module to the newly launched Sailiniq Space Station!
1739134535627.png
At the station, the first thing I did is undock the core module from the rest. Why? Cuz I realised only after I finished the previous mission that I didn't dock the core module on the right docking port of the second module. So, I'm fixing that here.
1739134595372.png
And there you go! The node is now in the middle, as it should be!
1739134611086.png
And the new module, with an integrated DG port, is docked!
1739134641595.png
The station, with the solar panels of the new module deployed. Sailiniq is now ready to welcome its first expedition!
1739134670097.png
And now, the return home.
1739134686554.png
1739134695126.png
"Wheel stop Houston."
"Copy wheel stop, welcome home Brunswicker!"

1739134717476.png
 
Made a shuttle-like skin for the Deltaglider using kitbashed sections of Wolf's Shuttle Fleet Photoreal textures, and man does it look hot! 🔥
1739196150646.png
1739196155123.png
That thing feels so much more real looking like that!
1739196161824.png
Oh, and speaking of, here is the DG docked to Sailiniq for Expedition 1:ROFLMAO:
1739196202420.png
 
Looks great! Especially the dark theme. How about making menu extensions by plugins or vessels?
For Launchpad configuration dialogs, that's not an option yet because it would require changing the whole Launchpad mechanism.
For when the simulation is started, there's a new oapiOpenDialog for addons to use but it makes me a bit uneasy since it could be prone to ABI/API breakage if we update the version of ImGui. I don't know how extensively the current oapiOpenDialog function is used in addons and if it could be a major issue.
 
For Launchpad configuration dialogs, that's not an option yet because it would require changing the whole Launchpad mechanism.
For when the simulation is started, there's a new oapiOpenDialog for addons to use but it makes me a bit uneasy since it could be prone to ABI/API breakage if we update the version of ImGui. I don't know how extensively the current oapiOpenDialog function is used in addons and if it could be a major issue.

Well, many of the few C++ developers use them and some many more would likely make use of them, if its much easier than today. After all, its also about the scenario editor.

I think an abstraction layer between Orbiter API and the actual UI would be the best way to go, since we could also switch the UI implementation during future development then without breaking the add-ons. Also this could be including in a Lua binding then. Maybe some more people would support the scenario editor or the launch pad, if it could be just edited in Lua, than C++ and ye olde Windows User32.dll.
 
Well, many of the few C++ developers use them and some many more would likely make use of them, if its much easier than today. After all, its also about the scenario editor.

I think an abstraction layer between Orbiter API and the actual UI would be the best way to go, since we could also switch the UI implementation during future development then without breaking the add-ons. Also this could be including in a Lua binding then. Maybe some more people would support the scenario editor or the launch pad, if it could be just edited in Lua, than C++ and ye olde Windows User32.dll.
The scenario editor is part of the core so it's not really an issue. The abstraction layer would be the solution but I'm afraid it would also be a major undertaking.
Since it's a screenshot thread, here is the scenario editor from my linux branch, with custom tabs provided by the vessel module :
scnedit.png
 
Back
Top