Recent content by ggalfi

Hi, I've never considered to connect a single joystick channel to two different input channels. Actually, one of the main motivations to develop VESIM was to make it possible to map my joystick's analog signals to RHC and either keyboard keys or joystick buttons to THC, hence I can use the two...

There are two easy methods to test IMU alignment: 1. Do a P52 with option 3. Use the offered star pair. If the optics, in CMC mode, finds the stars with reasonable accuracy (say, you can see them in the sextant), your alignement is good. 2. Open RTCC MFD. Download the active REFSMMAT (Utility ->...

A small, but interesting thing which I forgot to mention: as in the real mission, I did the LM deorbit through Erasable Memory Program. I struggled quite a lot with P99, till the point I looked up the most recent available EMP document (here...

I've only used the Orbiter2016 branch. At the beginning my main focus was on trajectory and decided that I would disregard the tighter consumables due to the non-J configuration. I had thought that I would address serious ECS-problems by my "divine influence" which ultimately needed only in the...

Hi All, I went through the full Apollo 15 mission with the goal to stick to the Flight Data File (that means 90% of cases the flight plan, but the individual checklists as well) as much as possible. Actually I did this with the missions 12 and 13 as well, but meanwhile I improved my technique...

I think so, yes. First, create the config files (see this post above). Then set THC lines in the appropriate config file (either CSM - Thrustmaster T.16000M.cfg.launchpad or LM - Thrustmaster T.16000M.cfg.launchpad) as following: THC Y Axis POV 0H FALSE THC Z Axis POV 0V...

Hi all, @jarmonik made a great improvement in OpenOrbiter to resolve the issue of objects sinking into or floating above the terrain. He also increased the max. lateral resolution with a factor of 8, so from now on the limiting factor is the quality of the original DTMs. You may find the...

I'm not sure about what's going on here. Albeit it is not desirable but a normal behaviour of Orbiter2016 beta - especially when the surface is really uneven - that the visual and physical terrain is inconsistent, sometimes up to a meter or so. On the other hand if earlier it was better for...

Honestly I don't know the answer because I've never got the opportunity to test this situation (I don't have two totally identical devices at home). It practically depends on how DirectInput handles your two Thrustmasters, whether it provides different names for them or not. I suggest to attach...

Yes, it is. Plug both joysticks in, open Project Apollo Configurator, click there on "Create Config Files" button. That will create the appropriate config files in Config\ProjectApollo\Vesim folder, if you have two controllers attached to the computer then there will be four new files created...

It is up to you whether you map the analogue signals of two different joysticks to the rotation and translation controllers' inputs or - as it is given in the config for the VKB Gladiator in the distribution - you can map the analog signal of one stick to the rotation controller, and the buttons...

Not everything which is connected to the USB, but the devices which are supported by Win's DirectInput interface. Practically all the joysticks/controllers which appear in Windows' "USB game controllers" dialog box could be picked up by VESIM.

Wow, that was bullseye :) In the attached scenario if I read out 411 it displays +10000, and your procedure also smoothed this problem for me. I cannot find any step in the Surface Activity Checklist which touches 411, but it could happen that during one of the previous V47s I typed...

@rcflyinghokie: Hi, thanks for looking into this. I was using mostly the documents on this page: https://history.nasa.gov/afj/ap13fj/a13-documents.html . For the LM I've used the Activation Checklist, Timeline book and the G&N checklist. I wasn't able to find the Lunar Surface Checklist for...

Hi all, I'm flying the nominal Apollo 13 mission, and now I'm at GET135 hours where - to prepare the LM for ascent - the AGS should be updated from the LGC. The problem is that when I do first V47 then set up the new time bias to 130:00:00, call 414+10000 on AGS, and press PRO, then nothing...