Jump to content

quelcertoleo

Members
  • Content Count

    40
  • Joined

  • Last visited

Community Reputation

10 Good

About quelcertoleo

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Richard, the product has been uninstalled and any backup has been removed as explained through the ticket email. I don't have any screenshots here but can provide them when I get back home. thank you.
  2. I have very good news for this issue. with the latest version 1.10.7.0 (I will not call it a patch) there has been some revision to the mechanism that loads textures, namely the problem is this one: https://flightsim.to/blog/flight-simulator-patch-1-10-7-0-breakes-liveries-heres-how-you-fix-it/ I had some liveries with this problem and, each time I picked them up in the profile->hangar I'd have a CTD or a simulator not loading (loading screen freezes). They always worked fine before this 1.10.7.0 version. All these CTDs are logged with the same code 0xc0000
  3. This post will create some drama, but I'm on the edge of tolerance with the above scenario. So, I bought Gaya's LIRQ scenery and, on my first flight, crashed with an invisible obstacle on landing. Discussion here: I was directed to Gaya support (and this is a first move which I don't like because I purchased from Orbx site, not gaya, when I have a problem with my car I don't go to Torino but to a car mechanic). I then opened a ticket (with screenshots and could also hand them a video) from their page (you can't open tickets or posts on the forum and that smells like rott
  4. is there an update to this issue? I didn't it noticed in any of the latest communications from asobo and how they are prioritizing bugs. in the meantime I tried many combinations with different planes, clean weather, no multiplayer and even no trackir in the Seattle area and I came to the conclusion that it is a problem with only this single scenery. I have in the area 1S2, KTIW and some other freeware sceneries. First I disabled every single scenery and left only KORS and I would get a CTD every time I get at about 10nm of KORS coming from any direction. Then I disa
  5. thanks for your input, I got a reply from their support: there you can see the poly that causes the crash, there are two more along the runway. if you disable crashes you will simply bounce 100ft in the air.
  6. you're right about the crashes, have the same problem in Donegal (the default scenario), everytime I'll clip the KA350 wing against the terminal. as for LIRQ, there are no other addons in the area all the way up until Bologna LIPE, this seems related to a custom runway profile. ticket raised to gaya anyway, thank you for the pointer.
  7. I had two crash with some unseen object when landing RWY 05 at LIRQ. I'm attaching also my settings for reference. It happens when landing during day or night and no matter the weather condition (live weather / clear skies preset) There are no other addons installed in the area. When approaching during the day I noticed that the runway had some sort of strange polygon issue with some parts of the runway visibly detached from other parts, like a disconnected/irregular mesh so to say. So far I had these crashes both with the TBM and Kingair, didn't try others ye
  8. I think so. But somewhere, deep in my heart, I'd like to hear "beta majestic dash" :)
  9. problem persists in 1.9.3. I had a similar problem with "vegetation polygons" not working in my own scenarios on 1.8.3 now in 1.9.3 they work again, not on OG20 though.
  10. bug still open in asobo (apparently) and crashes still happening: Error 29/09/2020 21:06:55 Application Error 1000 (100) Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f6cce4b Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f6cce4b Exception code: 0xc0000005 Fault offset: 0x0000000000e01825 Faulting process ID: 0x5a00 Faulting application start time: 0x01d69690a548eaf6 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Fault
  11. there was no mention about the fix in the patch notes but then I'm not sure if they would communicate these low level fixes in a generic patch notes. do you happen to have any more info or should I test it by trying to fly to KORS? :)
  12. In the linked topic above you'll see that I had a very similar problem to yours and I also have KTIW and 1S2 installed. Additionally I also have some other free scenery in the area. I tried disabling them all, every single one of them but, again CTD. There's one difference though, I can start at KORS without problems but I can't never get back to it. As a simple test, if you manage to start safely at KORS, could you please try to fly just a bit out of KORS, say go to Friday Harbor (FHR, it's just around the corner, 284.00 NDB) and then get back to KORS?
  13. don't do it: https://orbxsystems.com/forum/topic/199981-wycombe-air-park-egtb-scenery-not-loading-into-sim/?do=findComment&comment=1710741 additionally, as far as I know, MSFS loads scenery and prioritizes them by alphabetical order.
×
×
  • Create New...