Forum Posts

paden501
Oct 15, 2020
In Bug Reports
Austin, I think that I've discovered a problem with the wind direction in v1.2.7. The wind direction appears to be 180 degrees out from what the simulator AND the real life METAR data is reporting. See photo for more information, but here's the scenario where I noticed. I was sitting on the ground facing 270 degrees and the PFD on NobleSim showed that I had a 13kt tailwind. However, the windsock in MSFS2020 said that I should be seeing a headwind. I was using real time weather, so I checked the METAR using AWC, and sure enough the winds were reported 270 degrees. So, I double checked against the default G1000 wind reading; and again NobleSIM reporting exactly the opposite wind as the stock G1000. You can see this in the photo that I captured, where the MSFS G1000 is shown on top and NobleSim on bottom. I also noticed later in the flight that my course correction diamond on the CDI was on the opposite side of the track line as it should have been for the real wind (would be correct for the wind shown on the PFD in NobleSim was correct). This further leads me to believe that NobleSim may be reading in the wind direction 180 degrees out of what it should be. Please take a look into this and let me know if what I'm seeing is real on your end. Thanks Matt P
I think there's a problem with the Wind in 1.2.7 content media
0
0
22
paden501
Oct 04, 2020
In Bug Reports
Hi Austin, I gave MSFS a try on the new 1.2.7 version of the G1000 software today. Overall a very good experience (miles and miles ahead of Microsoft's implementation) but I did run into a couple of problems that I think are bugs in the software. For reference, I'm using the G1000 version of the software. The COM selector knobs aren't working on either panel. They work whenever MSFS is paused, and they work right at the beginning of a flight (before you touch anything else), but when the sim is active, the value just returns back to the previous value in the sim whenever you turn the knob. It's as if MSFS and noblesim are fighting over control of the frequency. Strangely, the NAV selector works just fine. I think you might have a bug in the hook between MSFS and Noblesim or maybe the sim is fighting against you for radio control or something. The Autopilot works great as long as you have it in an altitude commanding mode (so VS, ALT or APR). If it's in any AP mode that isn't commanding altitude (say HDG mode but without ALT hold), it causes the aircraft to violently shake up and down until the aircraft stalls and/or overstresses and the sim detects a crash, or until the pilot switches the AP off. I took a video that I can send you if it helps, but it should be pretty easy to recreate on your end. The OBS functionality isn't working at all in the G1000 version of NobleSim. I don't know if this is something that only got updated in the Cirrus version for 1.2.7, but the OBS button is still greyed out in the G1000, just like it was in 1.2.6. Same as my previous post, the Audio panel on the G1000 is non-functioning (I think you mentioned that fix didn't make this release). Otherwise, NobleSim is working great with MSFS. I put it through a few different approaches and aside from the issues identified above, the sim works just as well on MSFS as 1.2.6 did on XP11. My hat's off to the team on getting this integrated into the new sim so quickly, even if there are still some teething issues.
1
3
58
paden501
Sep 28, 2020
In Bug Reports
Hi Austin, I'm Matt. Don't think we've talked before, but I'm working w/ Derek (who I believe that you talk to regularly) on creating a sim setup using the NFS G1000 hardware and NFS 1.2.6. We were testing some approaches out last night and we ran into a couple of things that you might want to look at: The first thing I noticed is that the audio panel isn't communicating with XP11. What I mean by that is that when you press COM2 on the panel for example, it doesn't pass the instruction on to the XP11 panel the way you'd expect it to. I double-checked in the old SimControl software just to see if the instructions were coming through off the hardware and they were, so I believe the problem must be in the NFS software somewhere. When shooting an ILS approach, sometimes the CDI gets confused and treats the ILS like a VOR. That manifests itself in a couple of ways. First, the CDI states "VOR1" instead of ILS at times, and when it does that, changing the course also moves the needle alignment like it would with a VOR. I don't believe that's what would actually happen IRL though. With an ILS signal, it shouldn't matter what course your CDI is set to: If you're on the localizer, your needles should be centered. We were also noticing that when it did this, we'd lose the glideslope in some cases (it would disappear from the PFD). It didn't seem like it was ALWAYS exhibiting this behavior though. It seemed like it would happen primarily after we had shot an approach, run the missed, and then had come back around to run the approach a second time. It's almost like once you pass the ILS source over the first time, the instrument "tumbles" and then the software gets confused and treats it like a VOR. This one might be a real problem or it might be my lack of understanding the G1000 functionality. If I'm in flight with no flight plan loaded, and set direct-to an airfield (example: D-KPIT), I expected that I could then assign a procedure in the flight plan based on that airfield destination. However, when I tried that, no procedures show up in the PROC menu. It seems that the procedures are only showing up if you set up a flight plan with an origin and destination (e.g. KYNG-KPIT). Again, I've got to do some reading into the G1000 to see if this is really a bug or not, but I was expecting to be able to use Direct-to an airfield, and then that would constitute a flight plan that a procedure can be loaded on. Hey despite these hiccups, I think this software is great and it definitely is miles ahead of the stock XP11 G1000 implementation in XP11. I look forward to continuing to use this as we build out the rest of our sim. Thanks Matt P
0
2
50

paden501

More actions