Jump to content
Sign in to follow this  
Bob Scott

Lear 35 DME Problem

Recommended Posts

Observed this problem in the Lear 35 V1.9 in both FSX and P3D v3:  The DME indicator is updating very sporadically, and does not show changes in 0.1 nm increments.  I'll see something like 12.9...then it'll update to 13.9 without ever displaying the intervening 0.1 nm values (e.g. 13.0, 13.1, 13.2  etc).

 

Regards

 


Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

System1 (P3Dv5/v4): i9-13900KS @ 6.0GHz, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@30Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU, 1.2Gbps internet
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys2 (MSFS/XPlane): i9-10900K @ 5.1GHz, 32GB 3600/15, nVidia RTX4090FE, Alienware AW3821DW 38" 21:9 GSync, EVGA 1000P2
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, 2x TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Portable Sys3 (P3Dv4/FSX/DCS): i9-9900K @ 5.0 Ghz, Noctua NH-D15, 32GB 3200/16, EVGA RTX3090, Dell S2417DG 24" GSync
Corsair RM850x PSU, TM TCA Officer Pack, Saitek combat pedals, TM Warthog HOTAS, Coolermaster HAF XB case

Share this post


Link to post
Share on other sites

Observed this problem in the Lear 35 V1.9 in both FSX and P3D v3:  The DME indicator is updating very sporadically, and does not show changes in 0.1 nm increments.  I'll see something like 12.9...then it'll update to 13.9 without ever displaying the intervening 0.1 nm values (e.g. 13.0, 13.1, 13.2  etc).

 

Regards

Hi Bob,

 

I emailed Mark about this a couple days ago.  He got back to me and said he was not aware of the problem but he would look into it. 


"A good landing is one you can walk away from. An excellent landing is one you can taxi away from."

 

Bill in Colorado:

Retired

Comm: ASEL/AMEL/Instrument

CFI: ASEL/AMEL/Instrument

Share this post


Link to post
Share on other sites

Looking at the DME gauges closer, the coding is clearly broken...the tenths digit is unusable, which makes VOR/LOC/ILS-DME approaches a no go, not to mention any kind of arc procedure. 

 

Happily it was easy enough to fix.

 

Regards


Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

System1 (P3Dv5/v4): i9-13900KS @ 6.0GHz, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@30Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU, 1.2Gbps internet
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys2 (MSFS/XPlane): i9-10900K @ 5.1GHz, 32GB 3600/15, nVidia RTX4090FE, Alienware AW3821DW 38" 21:9 GSync, EVGA 1000P2
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, 2x TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Portable Sys3 (P3Dv4/FSX/DCS): i9-9900K @ 5.0 Ghz, Noctua NH-D15, 32GB 3200/16, EVGA RTX3090, Dell S2417DG 24" GSync
Corsair RM850x PSU, TM TCA Officer Pack, Saitek combat pedals, TM Warthog HOTAS, Coolermaster HAF XB case

Share this post


Link to post
Share on other sites

Any word from Flysimware on this issue?


"A good landing is one you can walk away from. An excellent landing is one you can taxi away from."

 

Bill in Colorado:

Retired

Comm: ASEL/AMEL/Instrument

CFI: ASEL/AMEL/Instrument

Share this post


Link to post
Share on other sites

+1


Raphael Chacón

158745.png

FLYSIMWARE-SM#1378797 RXP750-#1533812 RXP530-#1526291 RXP430-#1543520 

FS2C #43560 #52175 #68068 #68152 #69299 #71201 #72243 #105040 SM#1325481

PMDG #60260 #73469 #144746 #194702 #196953 #230831 #236231 #251801 #266742 #336381  #397556

Share this post


Link to post
Share on other sites

I found the issue. There was a piece of code in the DME 1 (copilot side) that did not get removed. The pilot side was correct. And this caused the copilot DME tenths to jump around. I will get this fix in our new updated tonight since i have not updates stores yet.

 

If you compare the 2 codes DME 1 had 100* 100% in the tenths code and DME just had 100*. This was suppose to be removed and not sure how i missed this.

  • Upvote 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...