richboy2307

Hi @Rick1486 I suppose this is the "STOP" sign you are referring to. This isn't tied into GSX or any other VDGS system, but is simply a static asset, the light on which comes on whenever night-lighting is activated. 2024-06-20 23-17-40(1).mp4 Thanks!

Hey @Rocket18 As you can see in this video, the jetways are certainly animated and functional normally. Are you able to request the jetway using the EFB controls on any aircraft? Ensure you do not have any conflicting GSX profile for KMIA(Folder location: %APPDATA%\Virtuali\GSX\MSFS). Try to disable the KMIA Jetways config from the FSDT Installer as below (remember to hit apply after making changes) Thanks!

The only thing I had done was select RNAV-W 14 via VAPMU transition. The waypoint IRPOD was already in my flightplan as the last enroute waypoint (as seen on simbrief screenshot). Selecting a procedure simply adds the points starting from VAPMU after it. IRPOD remains as a waypoint before it. (Ignore the EFOB - that is just because I was not at the departure airport when I took this screenshot). As Azlog mentioned above, this is likely because you dialed 10,000ft on the FCU and pushed in the knob at some point. As the new managed altitude was higher than previously planned CRZ Alt, it will update to the new CRZ FL as entered on the FCU (10,000ft in this case).

Please use this link: https://discord.gg/jE8neVcUZr It is as shown on their website: https://www.rwprofiles.com/ Thanks!

Thanks, bug is logged.

Hi @meierblom In 'Legacy' interaction mode you can push/pull the knob based on the small arrow that shows up near the top and bottom of the knob. Left click on your mouse will move the knob in the direction of arrow shown (push for up arrow, pull for down arrow).

Thanks for the report, shared with the team.

Hi @Lars Erik Axgren Please see here:

Hi @WallyWalt What you are noticing on the plane is actually correct for this aircraft type, as you can see in this IRL power-up video from an A320. Thanks!

Hi @Henni100 / @Rudderduck It seems it was missed out in the last update and needs to be re-uploaded with the new version. In the meanwhile please find the file attached below. Thanks! ENKB_GSX Profile.zip

Thanks for the reports all. Next time this happens, could you guys go into developer mode and check if there is any WASM module crash? If yes, please copy-paste the message here so it could help to narrow down the faulting module. Instructions on how to access the console: Enable developer mode (Settings > General > Developers > Developer Mode - ON) Open the console (Press the ` key on your keyboard or from the top DevMode toolbar via Debug > Console) On the search bar type WASM, and look for error messages (marked with red crosses). YOu can use the filters on top (red box) to make it easier to find them. Look for error messages such as 'WASM: Exception...' or 'WASM: Module...'. You can click on it and hit the 'Details' button on the bottom to get more information. The WASM crashes related to the a300 will mention 'inibuilds-aircraft' or 'a300' in them. Press the 'Copy' button to copy the selected message to your clipboard, and then please share them here, such as example: WASM: Exception c0000005 in gauge Systems in module vfs://inibuilds-aircraft-a300-600/SimObjects/Airplanes/inibuilds-aircraft-a306f-pw/panel/inibuilds-A300.wasm As we haven't been able to reproduce this issue internally or via the testers as yet, we'd appreciate this information to help with the investigation. Thanks!

Thanks for the write-up. I've shared with the team for further investigation.

Thanks, yeah this is an issue with the GSX profile as the location defined in them doesn't match the 3D model of the VDGS. Bug is logged, thanks!

Hi @ricardo Thanks for the suggestion. Will share with the team. In the meanwhile you could try to use the flood lights/dome lights to help combat this to some extent, as that helps to reduce the contrast and thereby lessen the "Eye Adaption" effect that MSFS has. Thanks!

Hi @Sebibue62 Sorry to hear. If you were charged for the scenery, but still have not received it via iniManager please reach out Direct Support here with the payment proof: https://inibuilds.com/pages/contact In case there was no payment taken, then the checkout was not successful and you need to try again. Thanks!

Hi @RedBenny Could you attach a screenshot or short video clip of when you notice this issue? Can't say we've seen this internally or reported by other users. Such media will better assist to find clues as to what is going on. Thanks!

Hi @mark cockburn Can you share a short video clip of the issue? Please try to toggle 'reverse on axis' off then on again to reset the calibration. Also please see calibration guide here: Thanks!

Hi @Reaver This was a simulator bug that caused certain content to not appear on the sim. Per Microsoft, this has now been resolved. You can read more about it here: https://forums.flightsimulator.com/t/resolved-missing-marketplace-items-after-latest-update-june-2024/646029/62 Thanks!

Hi @diogocec, The ''Rudder Controls Tiller'' is bound to 'Rudder Axis' itself (red box), and not the yawing commands (green box) which is what is used by default sim keybinds. You could also try to assign buttons to the tiller itself, such as 'INCREASE STEERING' and 'DECREASE STEERING' keybinds if you want to control it separately to the rudder. Thanks!

Hi @falcon71 Thanks, this is a reported bug and will be addressed in next update. Thanks!

Hi @falcon71 It depends on the charts, some are pre-programmed on TRUE courses in the database, but as a general rule of thumb it is calculated with MAGNETIC courses as default. The drawing on ND is equally done on MAGNETIC course, however the AP will make corrections taking into account things like wind. However it does seem like there may be some discrepancy here based on the MAGVAR, so I've shared with the team for further investigation. Thanks!

Hmm. @Superdraco2 Can you please confirm what was your FPS at the time you noticed this LNAV tracking issue? You can check your FPS in the sim by enabling Developer Mode. Then from the Devmode Toolbar on top, select Debug > Display FPS. Please share a screenshot of the FPS window during the time you have this issue. Thanks!

Yes, the stuttering can be caused by bad/missing Bing data. MS were temporarily having a Bing Data Outage at the time, but should be resolved now. Thanks!

Hi @Postman306 Try to disable photogrammetry and then enable it again. This seems like the terrain data for this area hasn't been loaded into your sim as yet. Alternatively, you can also try to clear your Rolling Cache (if enabled) and clear your scenery indexes (see here) and try again. Thanks!

Hi @Bachal For the radio panel you should be able to swap frequencies with the default simconnect event (COM1_RADIO_SWAP). You can read more about them here. But if you wanted to do it via LVAR, then it is (L:INI_CPT_VHF_TRANSFER_SWITCH_COMMAND) and (L:INI_FO_VHF_TRANSFER_SWITCH_COMMAND) for CPT and FO side respectively. You need to toggle the bit state (between 0 and 1), rather than write a specific value to it, for example below in SPAD.next: