Search results

When I tried to fly Apollo 9 circa two years ago, I also struggled with the lack of documentation. It became especially important when it came to SPS burn, where the stability of the control law was tested by intentionally adding a periodic deflection to the normal control signal of the engine...

Hi, first of all, feel free to tag me in your post, otherwise I don't get any notification on new posts here. The odd terrain on the pic is likely caused by Orbiter2016. You're supposed to use Orbiter Beta because this version is able to handle fractional elevation resolution - most of my...

I guess it is a factor of two, and the cause is that I used 0.5 m vertical resolution for the elevation. The non standard scales are handled correctly only by Orbiter2016 Beta. Currently it is only a recommendation in the documentation, so I think I should modify it to clarify that this setup is...

If you want to celebrate the 50th anniversary of the flight of Apollo 16, you may download the the scenery files from my site. There is one novelty: as I've promised to @4throck , beside the usual overhead illumination texture, I gave a try with much lower sun position (at circa 40 degrees, so...

Seem to me it was down since 28th Feb. I've restarted it right now. Thanks for notifying me!

This thread could be used to discuss NASSP's alternative joystick manager module, called the VESIM. As I was the one who began to develop this module, I am happy to answer questions here. Suggestions are also welcome, however please take into account that at the moment the time is not amongst...

Hi Miriam, I have made a lot of effort on determining the connection between the Apollo-era coordinate system and the LROC's. I consider latter as reference and made my textures conformant to this. So in this sense, if you look up the coordinates of an object in the LROC data, then you will...

If you mean the textures from this URL: http://www.absimp.org/orbitersim/apollolandingsites.html then the zip files (both surface textures and elev) should be extracted into Orbiter's main folder, and everything will go to the proper place. Some additional setup may be requried, please see the...

The input action will be processed only by the focused vessel. Feel free the assign the same joystick axis or button for both the CSM and LM even to different VESIM inputs, it shouldn't make any trouble. Yes, it works in the same way as it works when you are typing into DSKY with the keyboard...

I greatly appreciate your interest towards this VESIM module, so it is definitely not pushing your luck to ask questions about it. I don't know what you mean on "no coding experience" but currently adding new VESIM bindings means practically C++ coding. I said in one of my previous post that...

You have discovered some pattern, don't you? :) Yes, I've already begun to review the Descartes DTMs available on LROC site , and they are quite pretty, on one of them even the House Rock is clearly visible. So the goal is to make the "mysterious and unknown Descartes highlands" be discoverable...

As you may guess my original plan was to acquire detailed enough DTMs, so all the craters would be visible in 3D. And as you see, this plan failed to some extent. I have a few ideas on how to cure this thing, also I have got some promising results with Ames Stereo Pipeline's shape-from-shading...

Made all the Vesim bindings for the DSKYs both in CSM and LM. Tested it with my VKB Gladiator stick, there is enough button on it to cover all the DSKY buttons, and it worked nicely. It is still in my own repo (you can download it from here: https://github.com/ggalfi/NASSP/commits/vesim ). I...

It looks good. There is another test which you may try with the current version: for the LM I have already added the PRO button to the available VESIM inputs. The reason for doing that only for a single DSKY button was that I wanted all the CDR's action between the start of P64 and touchdown...

Currently the DSKY keyboard is handled driectly by NASSP, outside of the VESIM module. It is a development task, but wouldn't be difficult for me to add DSKY support to VESIM. However I'm not sure that a touch screen is considered as joystick device by DirectInput, as required by VESIM. You can...

Hi, sorry for the belated answer. Yes, you should add that line if it is missing.

Thanks for your kind words! Yes, it is a known problem and it is not your fault, and neither mine, as far as I can judge. The problem - I think at least - is rooted in different resolutions used by the graphical and physical engine. The solution would be to tweak the core module of Orbiter to...

As Thymo mentioned, it is included, and yes, you have to adjust the config files manually (GUI for that is also on my ToDo list, the problem is that I'm a less then moderate and less then enthusiastic UX developer :) ). Technically the PA Configurator can create the config files for each...

A few month ago I pushed a configurable joystick interface into the Orbiter2016 branch of NASSP. I've merely focused on the LM to make it flyable during P64-66 solely by a many button device like an X-Box controller or my VKB Gladiator stick. However I also implemented the most important...

Dear Dr. Schweiger, it was only a few weeks ago, when I made a not-so-well-thought promise on NASSP IRC channel, that when I'll be a billionaire then I'd buy a yacht for you to make Orbitersim open source. I'm not (yet) a billionaire, but I surely owe you at least a beer :) Thank you for all...