August 4, 20214 yr Anyone else tried these two at the same time? At the moment, I get a CTD after hitting "Fly" from the world map with both of these active. No issues with either one but not the other active. Not sure where to go from here, report it to FBW, or to Roman Design? Both? Thanks, ...jim ASUS Prime Z790-E, Intel i9 13900K, 32Gb DDR5 Ram, Nvidia 3090 24Gb, Samsung 970 EVO Plus 500 GB and 1 TB, Samsung Odyssey G9 Ultrawide 49" G-SYNC Monitor.
August 4, 20214 yr I'm not getting a crash. Maybe try a fresh install of the FBW Neo? Edited August 4, 20214 yr by Tuskin38
August 4, 20214 yr Yup i am getting the same with the A320NX dev version for the last couple of days. updated it on each occasion, even followed their guide to remove some other files in a folder, but it still CTD@S on pressing the fly button, I also tried with both default airports, no liveries other than stock, no change so far. AMD Ryzen 7 5800x3d, MSI X570 Pro, 32 gb DDR4 3600 ram, Gigabyte 6800 16gb GPU, 1x 2tb Samsung NvMe , 1x 2tb Sabrent NvME, 1x Crucial 4tb Nvme M2 Drive
August 5, 20214 yr Author 2 hours ago, Tuskin38 said: I'm not getting a crash. Maybe try a fresh install of the FBW Neo? One of the first things I did, including following FBW's full uninstall and clean install instructions. Also have nothing else in the Community folder (love that Addon Linker!) and all updates applied from Marketplace and Content Manager. Dang it. I was hoping it was not a some are ok, some are not thing. Sigh. ...jim ASUS Prime Z790-E, Intel i9 13900K, 32Gb DDR5 Ram, Nvidia 3090 24Gb, Samsung 970 EVO Plus 500 GB and 1 TB, Samsung Odyssey G9 Ultrawide 49" G-SYNC Monitor.
August 5, 20214 yr Author 1 hour ago, Car147 said: Yup i am getting the same with the A320NX dev version for the last couple of days. updated it on each occasion, even followed their guide to remove some other files in a folder, but it still CTD@S on pressing the fly button, I also tried with both default airports, no liveries other than stock, no change so far. Well, at least I'm not the only one. I'm hoping an FBW dev or Roman might drop in and give us a hint of a direction on what to try to resolve the issue. ...jim ASUS Prime Z790-E, Intel i9 13900K, 32Gb DDR5 Ram, Nvidia 3090 24Gb, Samsung 970 EVO Plus 500 GB and 1 TB, Samsung Odyssey G9 Ultrawide 49" G-SYNC Monitor.
August 5, 20214 yr 6 hours ago, JimBrown said: Anyone else tried these two at the same time? At the moment, I get a CTD after hitting "Fly" from the world map with both of these active. No issues with either one but not the other active. Not sure where to go from here, report it to FBW, or to Roman Design? Both? Thanks, ...jim I've had crashes with the FBW a320 that were caused by an addon livery. Try loading just the basic FBW livery. Lee Lee H i9 13900KF 64GB Ram 24GB RTX 4090
August 5, 20214 yr 7 hours ago, Midnight Music said: I've had crashes with the FBW a320 that were caused by an addon livery. Try loading just the basic FBW livery. Lee Tried that Lee, I use the addon linker so i can just load what i want at any one time. With just the A320NX in the community folder, it still causes a ctd as soon as i press the fly button. And that's even just using default airports, and the stock FBW skin. But i'd like to point out i have not tried any of Roman Designs Addons, but to be fair, if i am having trouble with any a default airfield, i doubt it's down to the addon, and for me it looks more like an issue with the A320NX dev. Just need to give them time to look at the issue. Edited August 5, 20214 yr by Car147 AMD Ryzen 7 5800x3d, MSI X570 Pro, 32 gb DDR4 3600 ram, Gigabyte 6800 16gb GPU, 1x 2tb Samsung NvMe , 1x 2tb Sabrent NvME, 1x Crucial 4tb Nvme M2 Drive
August 7, 20214 yr Author Well, it looks like either an FBW update, or Hotfix 2, resolved the issue. I can now load in to Roman Design CYOW with the FBW A320NX. Yay! ...jim ASUS Prime Z790-E, Intel i9 13900K, 32Gb DDR5 Ram, Nvidia 3090 24Gb, Samsung 970 EVO Plus 500 GB and 1 TB, Samsung Odyssey G9 Ultrawide 49" G-SYNC Monitor.
Archived
This topic is now archived and is closed to further replies.