richboy2307

Hi Yes there was a conflict caused by Horizon Simulations (HS) 787 as it modified some default simulator files that affected other developer's EFBs as well. This has since been resolved by HS devs, so please ensure you are on the latest version of their product. Thanks!

Hey @janjoensson Thanks for your feedback, unfortunately this is not likely to be changed. We recommend instead turning down the AI traffic density in your settings ( Options > General Options > Traffic > AI Aircraft Traffic Density )

Thanks, reported.

Hi, just to confirm, you are having this issue as of 1.1.1 HF1, wherein if you exit a hold, the FMC freezes (aka WASM crash)? Can you please let us know if you are able to recreate this issue? If this is specific to a certain HOLD procedure (at a specific waypoint), or happening universally across holds for you? More information would be appreciated. Thanks!

Hey @LukeFF, can I just confirm if you have cleared the scenery index between switching textures?

Hi, I just checked and am able to use it just fine using my xbox one controller connected. Please note that with PC mode enabled, the triggers wont allow for acceleration/deceleration on the controller itself (as by default the triggers are assigned to rudders, instead of toe brakes). This will only function if you have rudder pedals with toe-brakes connected, or if you assign your controller to toe brake functions (Left brake axis and Right Brake Axis on the controls) Thanks!

Thanks for this, noted and reported! I loaded up at FACT to check. And can confirm the RMI is reading the TRU bearing instead of MAG bearing. Need to adjust the data source for the RMI.

Thanks, reported.

Please ensure you have cleared your scenery index after the update. Also ensure you have enabled Photogrammetry in the settings. Thanks!

Probably a case of fallback to the wrong engine's textures (i.e. still referencing GE engine spinner textures). I would start by checking the 'texture.cfg' in this livery's folder, and make sure it is similar to another PW PAX livery, like the inibuilds house one, that is working as intended.

Awesome, hope you had a good one!

Should be fixed as of 1.1.1 HF1. Thanks for the video. I'll pass on the feedback.

Hi, are y'all still expriencing this issue as of v1.1.1?

Hi, Yes it is recommended to re-install after every update. Yeah the prompt is worded wrong. I'll raise this with the team. It should only delete the optimised texture pack (i.e. the "inibuilds-aircraft-a300-600-lowtextures" package from your community folder). Thanks!

Hi @MD82, can you check if you are still experiencing this as of v1.1.1 HF1? Specifically, the "HF1" part as the 1.1.1 that released originally on 13 Apr did not have CTD fixes as to amending procs/hold in it correctly. Thanks!

Can't say i've seen this before. Do y'all have any keybind that you are using for the FD per chance? Also are you able to re-engage the FD1/Standby Horizon afterwards, or its completely unresponsive?

Thanks I'll report these. @SiRuS T Some liveries are missing the info, but not all. In case you don't see any information whatsoever, please try a reinstall.

Hi @Fab10, thanks for your report. Can you confirm are you using Navigraph or default navdata? Seems like the issue is that they are not assigned to a specific runway so do not load as intended. We'll look into this, thanks!

Thanks this is reported already. It only SYNCs the very first METAR's data, not the updated ones. Thanks!

Thanks, this is being worked on.

Yeah that was a backend issue still pushing out the older version. Version 1.1.1 HF1 should be the update that was *actually* supposed to go out with the fixes as listed in changelog 🙂

Hi, @cu206wrc & @Vee1rot8 can you please confirm if you are still having this issue as of 1.1.1 HF1 update?

Thanks for your post. People with real world experience on the type are consulted throughout the development process. Naturally, as the product matures and the userbase expands, so does the product's exposure to even more individuals with varying real-world experience on the type to those initially consulted. The feedback naturally also evolves into more specific items and we continue to improve the product on the basis of this feedback. We're sorry if improving this product and taking action on user bug reports has brought any inconvenience to you.

Can you confirm you have Photogrammetry enabled in settings?

What are your scenery config options? Does this also happen with items like "Terminals - People", "Landside Cars" & "Animated Airtrain" disabled? Here is a video of me floating past in drone cam with no noticeable immediate change in FPS across this area. (Specs: AMD 5800x3D. RTX 3090, 32GB RAM) Maybe if you can share similar videos with the FPS Counter (enabled in via Developer Options > Debug Menu > Display FPS). Also try to clear your scenery indexes, reduce Terrain Level of Detail settings (100 or lower) and empty you rolling cache (if using any). For clearing scenery index: 2024-04-24 18-26-39.mp4