Jump to content

diamonddriller

Members
  • Posts

    199
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by diamonddriller

  1. @Coop"Those files aren't part of the provided installer, they are generated as the aircraft loads the config for the first time." Thanks Coop. Actually, I did wonder whether that was so. Not to worry. Everything works.
  2. @Pils Fair enough. Point taken. I'm getting old and impatient
  3. I am a little surprised that no one at X-Aviation has checked the installer for 2.0.1 (sorry about missing the dot in the title), as I have tried it more than once, and the same error was repeated. As the installer is actually downloaded each time from the server, I can't have a faulty large zip file..... X-Aviation's installers are pretty much rock-solid always, which is why I'm surprised. If I'm wrong, I'm sorry, and would appreciate an explanation as to why this happened. OK - I fixed it, and I guess other Intel users have either not had the problem, or fixed it themselves, or never had the plane!
  4. The only file in "settings" is "a.txt" in most of (if not all - I forget now) the regular and G500 versions - including the turbine ones. So, all the settings aren't loaded, and (of course) it crashes the Intel iMac. I corrected this by copying the config, etc. files over, and setting the disable MTU to value 1.
  5. @Pils " M3 Max? Personally I wouldn’t go any less if simming is involved." I absolutely agree. The Max will be well worth the extra money, and will future-proof the computer for some time. I'll have to wait a bit. Maybe they'll announce these Studios in the March-May 2024 - but who knows? You are, of course, correct about the graphics cards in Intel iMacs, which have been just about adequate going back for years. Well below the PC equivalents for the same periods. My 2020 iMac runs XP12 pretty well, actually, but Coop's Cirruses are very resource hungry.
  6. Yup. If I re-enable the mtu, X-Plane immediately crashes - which we've already discovered. I tried it again (now on 12.08b1), which makes no difference - well, it wouldn't! So, I slid sliders to minima, got 60+ fps at 1920x1080, and the flashing pretty much disappeared. So, in XP12, I can fly in a lower res, with no buildings, etc. and use the Entegra Oh, well....... This iMac does have a graphics card (AMD) with 16GB of VRAM, and it's no slouch with other planes. It's absolutely fine in X-Plane 11, with not a hint of any flashing, but 11.55 tends to run at 60fps anyway, for a lot of the time. I'm waiting for the M3 Studio, and I may have a punt at that. We'll see Let me know if (or when) you get a "fix"!
  7. The flashing MFD is sadly still with me in XP12 only........ Admittedly, there has been no update to the plane, but X-Plane has moved on a bit. To remind you, I had disabled SVS and the MTU uploader...... As you are not getting a stream of similar complaints, I suppose I am in a distinguished minority
  8. @CapetonianSee my apology re the rudder gap in the .org forum!
  9. @Capetonian Admittedly only tried this livery, but where's the massive gap between the rudder and vertical stabilizer? I'm using a Mac. I think you are being very harsh in your criticisms. LES has produced great planes for this sim. Errors creep in, and minor graphical inaccuracies are no big deal. I usually sit in the cockpit, not outside
  10. Well, I changed all (SR20, SR22, SR22T) Entegras and G1000 varieties to svs=0. I could load them up without crashes, but I couldn't change from one Cirrus to another without a crash. I could change back to a 172, but it then crashed if I went to another Cirrus. A bit odd. The G1000s still look OK. Sadly, the Entegra PFD is flashing still, in all varieties. I tried disabling plugins like Python, FlywithLua, ARO, etc., and that did not help at all. I had a look in XP 11.55. All Cirruses load properly, and I can swap without a crash. The Entegra PFDS are all rock steady. I took a look at the settings.cfg and svs=1 in the XP11 set-up. So, something in XP 12 does not like the Entegra PFD, and the loading of the planes is more flaky than in XP11. I guess you have all the info. you need to see what may be happening. As XP11 works OK, it can't be an AMD thing. If you can find out what's going on, it would be nice. In the meantime, I can use XP11 if I am desperate to fly the Entegras! I don't mind that, as I have 11 set up very nicely.
  11. Actually, Cameron, I had already done that a while back (maybe I missed one?), and on the Islanders - which were fine. I remembered the mtu problem, after you reminded me. I loaded a Cirrus Entegra today, without a crash, and without a 172 first! The bad news is I got a crash with the SR20 G1000 after loading a 172, and my settings.txt was correct. Anyway, the Entegra PFD is still flashing, and (to make life easier), I downloaded minimal scenery, to see if a better frame rate would cure things. Admittedly, 27 fps isn't great, but it should be enough. X-Plane 11 is so much faster.... The TorqueSim planes are always very heavy on frame rates. So, here are some more files and another thrilling movie for you and Coop to look at I believe you are in FL, and, if so, will not have a bad time with the hurricane! 906739076_SR22_AVIDYNE_DFC90-2023-08-2912_39_19.avi Log.txt CrashLog.txt settings.cfg
  12. Updated to XP 12.0.6b7. All the Cirruses (and I have the 20s and the 22s - G1000 and Entegras) crashed X-Plane, but I thought I'd try loading the Laminar C172 first, and that cured the problem. FYI, I've included the crash log, which may show why I need to load the Cessna first. However, the Entegra's PFD is flashing, and that was the same in b6 yesterday. 1709617353_SR22TN_AVIDYNE-2023-08-2900_04_49.avi crash Log .txt Log.txt
  13. @Cyber Copter If you read the update notes, you will see that Coop removed the beta range.
  14. @Cameron After what Coop said, I won't bother editing the XP11 files! Thanks for the reply. @Coop Thanks for the explanation. I would venture that the majority of Mac customers are still on Intel Macs, so your testing comment is a tiny bit worrying, but I suppose you know that things will still work. I'm going to stay put till the M3 chip is in play. My 2020 iMac runs both XP11 and 12 very well - and everything else that I use a computer for - so I'll hang on!
  15. Cameron, as you are looking at the thread, I did ask why the Cirrus and Islanders were affected by the multi-threaded-uploader problem for me in XP12, but not in XP11 - and more so, because the original support article was written for XP11. I'm not a programmer(!), but was just curious about the phenomenon. I'm sure the answer is way above my "pay grade", but I wonder whether this is (a) fixable, and (b) whether it really makes much difference if it's not. I have to say that my frame-rate seems more than reasonable with the alteration to the settings.txt, but then I can't compare it to what it might have been .
  16. @Pils Very interesting. Thanks for that. It seems to have worked! I also disabled XGS, even though I had the latest version, which should be OK. Maybe I'll put that back. What is very strange is that the multi-threaded-uploader has not caused any problems with the Islanders or Cirruses in X-Plane 11 on the same computer - and the value is "0" in those settings.cfg files. So, X-Plane 12 is mucking things up a bit...... By how much the performance has been degraded by disabling these functions, I have no idea. Maybe Cameron or Coop will comment.
  17. Crashing on my Intel iMac immediately, and the BN-2B does as well. Log.txt
  18. I agree on the overly sensitive castoring steering. I'm having to just caress the brake pedals on the TPR, else I'm all over the place. Even doing that, it's tricky. I have many hours in DA40s (RW), and, believe me, they are much easier to steer on the ground! Perhaps I will tweak the brake pedals sensivity, and that may well help. However, X-Plane has never been that good for taxiing....... Never mind. It's a great plane. Thanks.
  19. Hi. Should we update in XP-11 as well, or is this v 2.1.0 specifically designed for XP-12? I haven't downloaded anything yet, so haven't examined the file structure! 30 minutes later: Sorry - installed for XP-12, and saw it had a version for it. So, I did it in 11 as well, and - yes - it identifies itself as an 11 version!
  20. OK. So I may as well leave my XP11 version as is, and put 2.0.0 into 12. Thanks Cameron.
  21. Thanks Cameron. I've just had another look, and everything is as it should be. I downloaded 1.2.0 with no problem. Obviously a glitch - maybe I tried it before you had reset the link. All the best!
  22. Hi. I think it all worked on my Islanders, but I was not sure because none of the file modification dates for the G5 look any different from earlier ones. So, to make sure I re-ran the installer, and then ran the G5 installer itself. Again, no changes (although the G5 installer shows today's date). However, I guess it did work, because the copyright date on the G5 screens was 2023!
  23. My link is not live. All other purchased links are in red, and get the "hand" when I hover over them. The G500 link is in small black print, and is not clickable.
×
×
  • Create New...