Jump to content

richboy2307

Staff
  • Posts

    1663
  • Joined

  • Last visited

  • Days Won

    83

Everything posted by richboy2307

  1. Hi Thanks for your patience. Other users have reported this is caused by an outdated/incompatible spinner mod. Please remove/update the mod. See for more details:
  2. Thanks for your report, its been logged.
  3. Same answer as posted in FS24 Support. See:
  4. Fixed as of v1.0.7 Update
  5. Apologies for delay in response, but issue is logged for further investigation. Thanks!
  6. Hi Sorry for delay in response. Missing Red Horizontal Lines on T5A Jetway extensions - Logged for the dev team, the bug was reproduced Missing Logos / Plain White on T5A Jetway extensions - We cannot reproduce this issue on either HD/SD textures or with/without terminal interiors (see above image for ref). - The issue maybe because of a package conflict - either duplicated EGLL scenery installed or another installed scenery affecting the model/textures used. - Please verify via My Library that no other instance of EGLL is active. - To rule out other addon conflicts, try running with just EGLL in your community folder. Rename your existing Community folder (e.g. _Community), create a new one and place only inibuilds-airport-egll-heathrow inside. Clear your scenery indexes and load into EGLL to verify. To restore after testing, delete the new Community folder and rename your old folder back to Community. New HSBC Logo Your suggestion is noted. However please understand that our scenery was made with best available references we had at the time during development and the logos at present reflect that. Advertisements in particular are dynamic by nature and will keep changing over time so there will always be an element of "inaccuracy" in that regard with the digital twin counterparts. Thanks!
  7. Hi We do not have any planned POI additions at the moment but your suggestion is noted for future development. Thanks!
  8. Hi No there are no hand-placed static aircraft with this scenery. Thanks!
  9. Hi, No we do not advertise the scenery as compatible. Thanks!
  10. Hi, This is by design. That area of the ramp and taxiways are not openly accessible. They're fenced off and guarded similarly IRL as well. Unfortunately due to sim limitations and particular layout of the runway, the sim-ATC or add-ons may try to route you this way but in reality will not be possible or issued either. Thanks
  11. Hey thanks for your report. Will forward to the team. If you have any additional reference photographs (IRL, not sim) to share, it would be helpful.
  12. Hey Liam, Thanks for your report. 'No Jetways Here' Due to a sim limitation we are limited to just 1 jetway per gate. We cannot attach multiple jetways to the same gate , nor can we to attach the same jetway to multiple different gates. You can see the same in the GSX Gate Selection menu. The gates with jetways are indicated with 1x/J. 'Invalid Jetway Data' These might be a GSX profile bug. These will be seen as 0x/J on GSX. So for the reported instances: 308/308L - The jetway there is assigned to main gate (308) while the side gate (308L) is stairs only. 'No Jetway Here' is expected for 308L. 207/207R - The jetway there is assigned to the main gate (207) while the side gate (207R) is walk-in only. 'No Jetway Here' is expected for 207R. 209/209L - The jetway there is assigned to main gate (209) while the side gate (209L) is stairs only. 'No Jetway Here' is expected for 209L. However I do see that GSX cannot access Gate 209 and showing 'Bad Jetway Data'. The jetway itself is working directly via EFB request or sim ATC request as defined in the scenery though. Gate 209 seems to be the only affected gate in the entire scenery. Logged this for the team. Thanks!
  13. Hi Sorry you experienced this, but appreciate the report! Hopefully your other flights have gone more successfully. The autosaves are only created if the option is enabled in the settings and engine is running. As you crashed before start, its likely why. Based on the screenshots, it looks like T7 Gate 4 (F4) at KJFK. We’ve tried spawning there ourselves. We also tested this multiple times on different PCs internally, but we haven't been able to reproduce the WASM crash with the information provided as yet. Attached is a video from one of our attempts. We have also tried with variations such as - No fuel & payload loaded - IRS still in alignment - IRS not aligned It would be helpful if you notice anything we could try differently, or if you could provide a similar video showing the console window open at the moment the WASM crash occurs for you. This information is essential for us to try to reproduce the crash and work towards a solution. Thanks! 2026-01-20 03-28-29.mp4
  14. Hi all, Red screens appear when a WASM crash happens. The WASM crash on the runway spawn is an issue that was introduced in SU4 and affects many WASM aircraft. For the A340, there's a potential fix available in the v1.0.7 update. We recommend updating to the latest version and trying again. If the issue occurs again, please submit a new post following the guide below. Make sure to include all the requested information, especially autosaves and OFP files if you have them. This information is essential for us to try to reproduce the crash and work towards a solution. There is no one-size-fits-all solution to WASM crashes as its not a "singular" issue. Most WASM crashes are due to corruption in sim memory, and each is unique to its circumstances hence why all this additional information is required to re-create the conditions that may lead to this. Thanks!
  15. Thanks team's aware of this intermittent TCAS issue as reported before, currently seen to be caused by erroneous simconnect traffic data in FS24 and looking into it along with Asobo/MS. Thanks!
  16. Hi, This is an old report. The issue has been resolved already since v1.0.4 Update in Nov 2025. Thanks! 2026-01-20 01-14-35.mp4
  17. Hi everyone Thanks for your reports. Our team has investigated the issue, from what we are able to see is that the connection is still open from our module (data is continually transmitting, and being listened to hence why control inputs work), however their module stops rendering the display in such instances. We have also raised the same with WINCTRL (previously WW) for further investigation on their end. We are hopeful a solution can be found soon. Temporary solution is toggle between Cpt or Co-Pilot side in SAP whenever you notice this. Thanks for your patience meanwhile!
  18. Hi If you're airborne, the option only appears whenever you are not in NAV lateral mode. So you can, for example, set current HDG and pull HDG knob first, then you will be able to activate the secondary flightplan. Thanks
  19. Hi, The accepted format is WPT/ALT in LSK L1, so try DATOK/410 for example. After you start climbing to the FCU selected ALT, it updates the CRZ ALT to the FCU alt as long as its higher than current CRZ ALT. You also get an FMS scratchpad msg "NEW CRZ ALT FLXXX" as seen here. The temps however you may need to adjust on your own. 2026-01-19 22-57-25.mp4 Thanks!
  20. Glad to hear. There is no option to disable that at the moment but suggestion is noted for the team. Thanks!
  21. That sounds like network issues with simbrief servers, if its taking that long for a download to complete. But anyways, as long as it works for you 👍
  22. Hi @KLEE330 Thanks for getting back. Right so your Simconnect connection is not working properly OR the addons are not able to write to your work folder. The OIS/EFB are not WASM so have their data cached elsewhere in the sim's browser instead of the work folder for WASM modules. As I mentioned, we haven't made any changes on our end that would affect the behavior, and we're unable to reproduce the issue on any of our systems running SU4. In this case, you should try running the simulator as an administrator with elevated permissions, verify that the work folder isn't set to "read-only," or adjust your Windows UAC settings to see if that resolves the problem. Additionally, you might consider repairing or reinstalling your simulator files to rule out any issues that may have occurred during the initial SU4 update process. Thanks!
  23. Thanks for your suggestion, shared with the team. As for the GNS530, that is based on actual L1011-500 retrofit configuration: (Click to enlarge image)
  24. Thanks, logged.
×
×
  • Create New...