KylerHolland

I was able to fix the problem. I brought the faulty part to an electrician. He disassembled the button and cleaned the contact surfaces. Shame on Honeycomb.

Hi, guys. I just received my brand new Honeycomb Alpha XPC. One button doesn’t work. it’s the one labeled “Avionics BUS2”.

I contacted support, but they haven’t replied yet. I wonder if anyone got similar problem. Any advice is appreciated.

P.S. I am not in the US and I had been waiting for 5 weeks until I got my Alpha XPC from China. So, I can’t return the controller.

37 minutes ago, Bert Pieke said:

I think the button only disconnects trim.  The thumb switch below it, is the electric trim.

The POH says that this "AP/trim disconnect" button basically disengages autopilot and electric trim:

Quote

AUTOPILOT DISCONNECT (A/P DISC/TRIM INT) SWITCH When depressed, will disengage the autopilot and interrupt Manual Electric Trim (MET) power. 

I guess, I figured it out. The button doesn't work in the game in a correct way. A custom key can not be assigned to it. Will report a bug. I mean you can assign "Disengage autopilot" but it supposed to be a little more than that. The button should also stop 'Manual Electric Trim' (MET) from functioning. In case of malfunction the MET can be switched off and the analog trim wheel can be used instead.

Seems like this button on the yoke has two functions. 1. Disconnect AP (autopilot); 2. Something with the trim, I guess. There is no such thing as "Disconnect trim", so probably some other trim fuction? I looked POH for 172 but there is no explanation.

Hello! I have Honeycomb Alpha yoke which is a replica of Cessna yoke.

I’m trying to assign the button on the screen below to the same button on my actual physical yoke. But I can't find it in the Controls menu. Can anyone help?

13 minutes ago, Romeo_Tango said:

Perhaps a bug to be reported through the 'flighting' forums.

It will be done. The tricky part is that you can't roll back sim10 update. I mean, you can do it via Steam, but in will not solve the problem. Only the complete re-install does.

I finally got it! The problem is with the sim10 beta update. I installed the game on my laptop and picked up beacons' signal during the very first test flight.

2 hours ago, MDFlier said:

 anyone able to hear the Morse code from any VOR, NDB, or ILS? I can't seem to make those work, either. Activating the audio for VOR1 (or 2), ILS, ADF1 (or 2), or MKR does nothing.at all.

I do hear them. In default Cessna 152.

2 hours ago, MDFlier said:

I have also tried to get the beacons to work, but even at locations where I know them to be active, selecting the audio for MKR does not work.

Do you have sim10 beta installed? I have it installed, may be that's why I don't pick up those marker beacons.

12 minutes ago, Romeo_Tango said:

Do you have Mods in the community folder?

Only single one. The mod that fixes taxiway markings at KMYF airport. Do you think it might be a cause of the marker issue?

10 hours ago, sd_flyer said:

I have opposite problem. Lol Tons of airports I shoot instrument approaches IRL marker beacons have been removed in and substituted with gps fixes

There might be a bug on my side. A few guys informed me about airports with marker beacons. I tried those but no signal there. No flashing, no beeping. 

1 hour ago, Mace said:

I just flew the ILS Y Rwy 12 into KMSO (Missoula, Montana) and it had marker beacons on approach.

Thank you very much, sir! I'll check that airport.

8 minutes ago, RandallR said:

Which aircraft were you flying and which nav or nav suite were you using?

Thank you, Randall! The aircraft is default Cessna 152. I just set the frequency for ILS at chosen airport and start landing there, waiting for beacon to flash and beep. The MKR button is on and the volume is at max.

6 minutes ago, RandallR said:

Markers (where they exist) are still going off for me in various aircraft and nav systems.

Hey there! Can you please name some locations? I mean where you recently picked up a marker beacon signal? I just tried at KONT and there was no signal for me. This airport has one inner beacon on RW 26L. I checked that with airnav.

21 minutes ago, charliearon said:

do you have the MKR button engaged on the audio panel in your aircraft?

Hello! Yes, I do. In Cessna 152. By the way, as I remember MKR button can be turned off, but the receiver will still flashing. Turning MKR on simply adds beeping sound.

Hello!

I bought a game a month ago. When I was flying around in Cessna 152 I used to notice my marker beacon's receiver flashing and beeping. About a week ago the receiver became silent. No flashing, no beeping. It took my attention and I decided to check the thing. I know that are not too many marker beacons left in the world but I found out that MCO airport still has inner beacon. RW 17L. Localizer 110.95. So, I tried a few landings there, but the marker beacon receiver is silent. Again, no flashing, no beeping.

Does some update might either removed markers from the game or temporarily turned them off?

Guys, if some of you fly around some airport with marker beacons, can you please prove that marker beacons still work? I would like to test that in my game, because there might be some bug on my side.

Hello!

I fly default Cessna 152 in MFS2020.

Recently I tried to do 1 hour flight with minimum fuel on board. LNM said that after 1 hour of flight my Cessna 152 consumed 28lbs of fuel. However, in MFS2020, when I opened toolbar and clicked on FUEL section it showed me different numbers. The game said the flight consumed much less than 28lbs, actually.

So, how does LNM count the consumption? Does it take the data from the game? 

Ok, I figured it out.

VORs have calibrated declination which is why I see two numbers on the bearing.

VOR's calibrated declination might be different from the magnetic declination in the area.

An example:

let's say we need to fly to the true north using VOR. Local magnetic declination is 11east. So, if we were to fly using just magnetic compass we would keep 349 heading. it's 360-11 = 349.

Our VOR has calibrated declination 15east. Which means we need to set CDI to 345 if we need to fly straight to the true north with the help of VOR.

So, if the MD is 11east and VOR CD is 15east then we will fly with CDI set to 345 while keep 349 on the magnetic compass. These are two numbers I see on VOR bearing as 345 > 349. 

Hello! 

I am planning an IFR flight and I noticed that when I measure distance from VOR to a waypoint it shows me two different numbers for magnetic radial. Like 360M > 4M. What does it mean?

Second question - I inserted approach path to land at the airport and it shows me heading 284 while the ILS says it is 281. Why there is a difference?

Hello, Alex! It is not a bug, I figured it out. I need to activate the first flight leg before taking off. The first flight leg becomes magenta and everything is fine! 

Hello!

I created a simple flight plan where I have the same airport as departure and destination. It looks like this KMYF N0101A040 CLSTR LNTRN TILRE HAILE KMYF

When I take off all the legs from my flight plan become grey. Like the flight is completed. I guess it is because when I am taking off I pass that "destination waypoint" and that's why LNM thinks the flight is completed. How can I fix that?

My flight plan is here https://drive.google.com/file/d/113sec8KG4RGL3AonDkK1stUkc2kTErmg/view?usp=sharing

1 hour ago, albar965 said:

You can either update the Navdata in LNM (and MSFS too) using a Navigraph subscription or tell LNM to use the MSFS navdata only by selecting "Do not use Navigraph Database" in the menu "Scenery Library".

Thank you very much for a fast reply! This worked for me! The software is awesome, I like it! Thank you for what you do, sir!

Hello! I am new to the aviasims world. So, I planned a simple flight in Little Nav Map. It is a direct flight from KMYF to Santa Catalina's VOR (SXC). I noticed that my Cessna can't catch this VOR. That's because in LNM VOR SXC has wrong frequency which is 111.40. The actual frequency is 114.15. I checked with SkyVector and MFS2020. They both have the correct frequency. I tuned to 114.15 and it worked! By the way this is not the only case. I noticed at least two more VORs with wrong frequencies.

Is there any way to correct that? 

P.S. I installed LNM two weeks ago, so it supposed to be up to date, I guess.