Omaniac

Normal. Do not confuse IAS/Mach hold in this aircraft with LVL CHG in the 737. When you press IAS Hold your autothrottle will go to CLAMP. All signals to the autothrottle are removed and you must control your throttles manually .A nice way to start a descent is to use VS and set around 2500 ft/m, let your throttles come back to idle and press IAS. Adjust throttles to make sure they are at idle. You now control your speed with the thumb wheel. Remember to set your speed window at the same speed as your throttles will come alive when you level off. This to avoid your throttles to "overreact" when you level off.

Not 100 % sure but I think a warning is generated every time you are set to land with less than a fixed value of 2000 kgs. The one you get. Then you have a different warning if you land with less than your diversion fuel. That is the fuel you have entered in the FMC. The fuel you enter in the FMC should be your final reserve fuel (30 mins) + fuel to alternate + any extra fuel. 1000 kgs is way too low, and you will then most likely go below 2000 kgs in your flight = fuel warning.

Nope, I base it on how smooth my head moves around the cockpit (I use TrackIr). The difference is not huge, but it is there. At 30 FPS my GPUs never get close to 100%, no matter what or where I fly. My CPU is never stressed and stays well below 100% no matter what I do.

The ailerons and elevator are not powered in any way. They are aerodynamically operated via servo tabs. In the real aircraft you need pretty large control inputs to operate the ailerons, and I don’t think you will find a MD pilot who have not ran out of elevator control during landing at least once. So, yes, inngeneral you need larger inputs to the ailerons, but less so with the elevator. I use force feedback controls myself, and ailerons are a bit difficult to control with these. I have yet not tried with the FFB disconnected.

I have pretty much the oppsite experience. The sim runs better with unlimited. My GPUs run at 100% or close to it, but that is what I pay them to do. Not laze around at 60%. 😀

But the Rift is not 4K. How is the readability with the Rift in the MD cockpit? I know in the PMDG 737 it is very hard to read any numbers, the FMC or the displays without leaning very close to them.

I have done absolutely nothing to my throttle settings. I advance, engage AT and thrust is set. From there on, nothing I do with my Logitech throttles affects the sim throttles. This last until I disconnect the AT and use them manually. Isn’t there a setting for this in the Load Manager (or sim)? Allow throttle (or controls) to override sim throttles or something like that?

No difference when I load from the P3D menu. I can change all other options, weights, sounds, etc, but not TG and RL. For that I need to shut down P3D.

A question about the LM. I can't enable/disable TG and RL "on the go". I need to shut down P3D in order to do this. Is this the way it is made to work?

No, not calibration. If I am not mistaken, you can adjust the intensity of the radar picture via the outer, black rotary switch on the panel where you adjust the PFD and MAP display intensities. If that adjustment is simulated. And you do need rain intensity strong enough to give a radar return. I’m not sure how well this is modeled in AS. I have seen returns myself, but they showed up in a position where I did not expect any.

Did you turn up the intensity for the radar? I was not aware the MD came with any routes?

Thanks, but this time it was the calibration of my pedals that went out of whack when I updated the MD. A P3D restart fixed the brakes issue and I had to recalibrate the pedals to avoid the aircraft from pulling to the right. First time this has happened to me, though. Sensitivity was already set to max.

Hmm, I have never had any issues with the PB in MD until I installed the latest version. Just one flight, or tried to, the brakes locked up and I could not taxi out.

I don’t see any cockpit lights blinking, I see your whole screen blinking? PC issues? Driver issues?

No, but I have noticed that sometimes the FMC jumps to page 2 after you execute DCT INTC. It looks like you have lost everything. Just select previous page. I think this is a bug.

Pressing and using the middle mouse wheel works with some efford. TAB is much easier.

And of you load without RL and TG? For info, I need to restart P3D to turn ON or OFF these features.

To me it looks like several bugs happen because people do things in the «wrong» order. They are still bugs, but I would never experience them because I never load a departure starting with the SID. Starting with the RWY is easier as most modern FMCs then remove all SIDs not connected with that RWY. Same as I will never get a problem intercepting a localizer because I will never neglect to set the correct frequency and course. Often I see Youtube videos with both course selectors set to 000. I had a discussion some time ago with a guy who had problems with a 737 classic add on. I told him to set up the MCP like in RL and he replied he did not fly it like in RL. So how he expected it to fly like it should is beyond me. The MD (and some other add ons) is so advanced you really need to do things the right way and in the correct order. But a bug is still a bug even if I will not be affected by it. 🤓

Are you able to access the website with your browser? Maybe you are on the US gov blacklist? 😛

You will not get any pitch mode unless you set a new altitude in the window, armed or not. So, the correct order is set new altitude and then select any pitch mode you want. This assumes you are in any level mode already.

You are wrong on almost everything.😀 VNAV is a pushbutton. IAS as VS as well. IAS and VS values are changed by rotating the thumbwheel. The heading button can be pushed, you will get Heading Hold. It can be pulled, you will get Heading Select. You then rotate to get the desired heading. And to top it off,I was wrong in assuming you were talking about the heading button. Now, the altitude button is a rotate, push/pull as well. Rotate changes the value in 1000 ft increments. Press TAB and rotate and you change in 100 ft increments. In the aircraft this is done by pushing the button and rotate. Pulling the button arms the selected altitude so the aircraft will level off at this altitude when the autopilot is flying. You can set this automatically in the load manager.

Press TAB and rotate as usual.

You set your minima with the orange bug on the altimeter. You set your DH with the knob you used. This is used low visibilty approaches only. In your case you set the orange bug at 190 ft and you need to monitor and understand that your minima in this case is 1190 ft not 190 ft.

Do you actually load the Mooney at the airport/gate you want to fly from, then switch to the MD? Or is the Mooney set in the P3D opening window and you load MD from there?

No worries, but I think Davide has most of it. I did submit a ticket regarding this issue. What is completely new is the fact that I got the same problem with FPS with only one card. That points to two different, non related issues. FPS problems not related to SLI (but maybe memory?) and lights issues related to SLI.