|
|
Post by emilio on Mar 6, 2022 21:52:30 GMT
My first time using the program I encountered a serious issue. The panels show up fine in VR, but for some reason I cannot interact with my NAV or COM controls. Radio switching also does not work. Very frustrating. When not in VR, everything works fine. In VR the only way I am able to interact with COM and NAV is to close the menu using the tab key. Once I do that, I can change frequencies. As soon as I press tab again and the VR menu comes on, no more NAV and COM.
Update: The G1000NXI I was using was on a DA62 mod. When I changed aircraft to a D40, the COM and NAV worked properly. When I switched back to the DA62, no COM and no NAV. In testing the program with the DA40, I came across the following issues: at one point MSFS just crashed, on another attempt the mouse disappeared and I couldn't get it back, On another try the G1000 screens went black and did not come back, on yet another try I got a dialogue box with a bunch of code that wouldn't go away.
As you might expect, my feelings about this add on are not positive. I love the idea. I don't like paying $35 for a program that doesn't work properly. I have a high end computer. NVidia 3080, 16 GIG Ram. I'm using the HP Reverb G2. If I don't get a response and a solution from support, I guess I'm out $35.
|
|
|
|
Post by Sam Smith on Mar 7, 2022 13:54:47 GMT
Hi,
SIM EFB generates a web page, which FS2020 displays within a panel provided by FS2020. I would find it very unlikely it could affect any other flight controls in the simulator, and if it did it would be on both VR and non VR mode.
FS2020 handles mouse management, and interaction in VR which is not always perfect but in recent releases has got a lot better but is beyond our control.
|
|
|
|
Post by emilio on Mar 7, 2022 18:23:52 GMT
So, what are you saying? That I don't know how to use the Garmin 1000? I'm telling you that since installing this program I've had nothing but issues: crashes, system freezes, blank screens, inability to work Garmnin 1000 COM and NAV. This should be easy to test. Try your program with the G1000NXI mod. Try it with the DA62 mod. I was willing to continue with the program knowing that I could always remove the menu and VR to get it to work, but even then MSFS completely stopped working. It just shut down mid-flight. My opinion is that something is going on that is interfering with the area just below the menu in VR. It doesn't make sense that all the other controls would work but not the ones close to the menu. It's as if there is another window atop those controls preventing interaction. I will say that when you hover the mouse over the controls, it shows that the control senses the mouse. It does change color. It just won't let you do anything.
I'll do some more testing when I get a chance.
|
|
|
|
Post by emilio on Mar 8, 2022 6:09:02 GMT
Okay, here's what I learned. The problem is definitely your program. What it's doing is when you have the menu open in VR, something is blocking access to anything below a certain point from the menu. On the DA62 I couldn't access the COM and NAV controls. On the DA40 you can't access the light switches. I'm sure you can test this yourself. It doesn't have to do with MOD incompatibilities. It has to do with whatever web page you were talking about getting in the way of what lays beneath it.
I did a test flight in a DA40. I had a bunch of issues right off the bat. I couldn't center the VR view. I closed out and tried again. Then I had some cursor/mouse issues where I couldn't get the mouse to appear in VR. I was about to uninstall your program right then, but low and behold, the mouse appeared. So, I continued with a cold start and a short flight to an ILS. I opened all three panels, including a moving map. The only issue I encountered was the disappearing mouse. It came back and I was able to complete the flight.
|
|
|
|
Post by egotroubler on Mar 8, 2022 17:19:23 GMT
well, 16GB looks like that could be the issue... it's what MSFS for itself needs to run halfway smoothly, not to mention running any mods or additional things in background. Did you check your memory usage? |
|
|
|
Post by emilio on Mar 9, 2022 1:29:00 GMT
I was mistaken. I have 32 Gigs of RAM. The problem can be recreated. See my last reply.
|
|
|
|
Post by Sam Smith on Mar 9, 2022 10:32:12 GMT
I am on Holiday currently until next week. It won't be memory issues, and like I say logically speaking it's hard to see how our program would affect other controls in VR only.
|
|
|
|
Post by emilio on Mar 9, 2022 17:32:32 GMT
Somebody help me out here. Anyone. Just try the examples I provided. I know it's not my machine. It has to do with whatever window SIM EFB is creating in VR. It will take you all of two minutes to test this.
|
|
|
|
Post by Sam Smith on Mar 15, 2022 9:08:56 GMT
I will try to test this tomorrow, had a lot of work to get through on my return. I guess the DA62 (COM and NAV button access) and DA40 (Access to light switches) are included in stock FS2020?
|
|
|
|
Post by Sam Smith on Mar 15, 2022 12:06:05 GMT
So I just did a test. I could recreate the problem if I did not dismiss the SF2020 menu before trying to interact COM/NAV buttons in FS2020. It only seems to affect certain controls.
So after activating the SIM EFB pannels from the top menu you need to hide the menu again by pressing TAB.
Not really a fault with SIM EFB, but just a symptom of using the menu.
|
|
