September 17, 200916 yr Not sure this is an error but why do the two instruments show a different distance to tuned VOR1?Whats your altitude durring that shot...?If your close to 25000 feet agl, then it could be the difference between slant range from the raw DME from the VOR station and the actual reference point in space that the FMS is calculating for the VOR waypoint at cruise altitude... An easier explanation would be... the DME is getting raw distance to the VOR from the plane (includes altitude) and the LNAV Waypoint referencing the VOR is directly above the vor but at the VNAV cruise altitude.JB Buzz313th
September 17, 200916 yr An easier explanation would be... the DME is getting raw distance to the VOR from the plane (includes altitude) and the LNAV Waypoint referencing the VOR is directly above the vor but at the VNAV cruise altitude.You are right. I was at fl170 at that moment. Calculated the thing with the pythagorean theorem and guess what: exactly the figures of my screenshot... So, PMDG, no error here, just another thing you have modeled very well.... :(
September 17, 200916 yr I'm sure that has nothing to do with PMDG, its FSX that is supplying the correct data not PMDG. Cheers, Andy.
September 17, 200916 yr Sorta, FSX provides the DME (slant range) but the distance to fix is calculated in the FMS dll, minor point but fair. Dan Downs KCRP
September 17, 200916 yr In reply to your post MatzeH84..Well I'll try that loading thing, thanks for your advice! Last 2 flights spoilers worked well with RPM 100%.. maybe this was the point (but if, is it correct that the spoilers don't deploy/ retract when RPM is not 100% ?)Two other issues that I recognized:The night lighting of the cabin: seems as there would be only a light in the back and one in the front (see pic); cabin lighting is turned on, off it's even darker.Is it correct, that if I turn the engines (or generators) off, batteries do not provide power to the panel illumination? Can't believe that there is always a GPU necessary to turn the cockpit lighting on ^^Regards,Matthias Hanel Regards. Matthias Hanel MilViz Beta Team
September 17, 200916 yr Just found the answer to my cruise altitude being ----- after entry and having to redo it from the previous page. It comes of not highlighting select after loading a flightplan. If I highlight select then the cruise altitude goes in with no bother at all.See.... knew it was something I was doing wrong lol. Might help others with the same issue though.John Ellison
September 18, 200916 yr Not sure this is an error but why do the two instruments show a different distance to tuned VOR1?I believe the difference is that the FMS (LNAV) shows the horizontal distance while DME can only report the slant distance to the station.
September 18, 200916 yr Don't know if this issue has been touched on specifically, but I get a CTD to desktop when I am trying to tune the Nav 2 to a different VOR when in the air. Seems to work on the ground, but twice now I have re-tuned the NAV2 and attempted to switch to it during flight and ..CTD.Very frustrating.But hey - great plane and fun too. I look forward to finding time each evening just to setup a flight and go for it. I haven't felt this way about FSX for some time so am enjoying the renaissance. Just love the Icing effects along the leading edges and nose cones. After so many years simming I have concluded I am not really interested in long flights in big iron- Just small to medium in the mid to small range aircraft - and this fits the bill perfectly.Congrats to PMDG crew for a terrific add-on.(Running win xp,Quad 6600 overclocked to 3gbs) 4gigbs ram, Nvidia GTX 260 graphcs card stock )
September 18, 200916 yr I recently had an issue with the main door.I loaded up the default Friday Harbour flight with the J41 and I landed on the runway off to the left. I parked the plane at the ramp and shut her down completely. She was out cold. I then connected external power and flicked the GPU switch to on. I then tried to open the door, but was I was hearing the sound of it opening, it immediatly closed. The Red door icon on the Ramp Manager goes to Green for a few seconds than back to Red. I also get the appropriate door messages at the top of my screen telling it's opening and then it closes after a few seconds.I look outside to see what happens, and same deal. I either click the door on the Ramp Manager or I hit Shift + E.... The door simply opens a tad bit and then closes shut right after that.I would assume this is a bug as the aircraft has the necessary power... but then again, it's a door, you open it manually right? Erik L.
September 19, 200916 yr Erik,Did you load up the default Friday Harbor flight with the J41 or with a default aircraft and then switch to the J41? Loading the sim with a default aircraft will cure all manner of odd quirks. Best Regards, Kurt "Yoda" Kalbfleisch Pinner, Middx, UK Beta tester for PMDG J41, NGX, and GFO, Flight1 Super King Air B200, Flight1 Cessna Citation Mustang, Flight1 Cessna 182, Flight1 Cessna 177B, Aeroworx B200
September 19, 200916 yr any news for a release date?!You are not going to get an answer to that unfortunately. \Robert Hamlich/
September 19, 200916 yr I then tried to open the door, but was I was hearing the sound of it opening, it immediatly closed.This is probably a manifestation of a known bug in FSX which occurs when the user aircraft is parked near a refuelling stand/trigger, when you open the main door the animation almost immediately closes the door again not smoothly but instantly and you can also sometimes hear the door closing sound going in a constant loop. Cheers, Andy.
September 19, 200916 yr Here's another CTD:I always get a CTD between 30-45 minutes of the beginning of the flight. It usually occurs when switching views. Actually it almost always occurs while switching views!-Kevin
Create an account or sign in to comment