23 minutes ago, HiFlyer said:

I adjusted the power limits (MultiCore Enhancement) which is probably what caused the initial heat spikes. This also caused me to buy the CPU frame to handle the extra temps from the higher power and to more carefully redo my aio seating.

I also corrected my initial mistake of not running my DDR5 at the full XMP max, which also seemed to have an effect on fps.

I believe my e-cores are running at 4.5ghz right now.

Also:

MSI motherboard?

Now you have to share your bios settings!

Thanks.

5 minutes ago, ConairMSFS said:

MSI motherboard?

Now you have to share your bios settings!

Thanks.

I think he has an Asus. I have MSI and set the CPU Lite Load setting from 12 to 5. I could possibly go lower.

https://www.youtube.com/watch?v=-mkAVITZoLY

9 minutes ago, Dazzlercee23 said:

I think he has an Asus. I have MSI and set the CPU Lite Load setting from 12 to 5. I could possibly go lower.

https://www.youtube.com/watch?v=-mkAVITZoLY

Gigabyte Elite AX

I'm having a real strange issue.  I opted into the beta, then reverted back to SU11 after deciding to wait a bit for things to smooth out.

Once back on SU11, I'm unable to choose a parking spot from the world map.  The "Set Departure / Arrival" pop up that's supposed to appear when clicking on a parking spot, just gets completely cut off.  I now have to choose the parking spot from the drop down menu.  

This was absolutely NOT happening prior to opting into the beta...so something during the install / revert caused it.  

Installed an hour after beta was released

I've got REX/AIG/PMDG/FENIX/FBW installed 

Installation went smoothly no issues

Noticed improvement in frame rates with the PMDG 738 giving me 60fps in DX 12 (3440x114p + 115% Render Scaling - Ultra settings + TLOD 250)  on initial load .. however i re locked the sim to 50 FPS.

Came across the PMDG parking brakes bug but managed to do the flight anyway since my default panel state has the parking brake "not set" as the default so its just being held by the chocks. I can live with that till a patch comes out.

I usually fly with  the RTSS overlay and in dx 12 mode Asobo clearly moved some cpu utilization workloads around. In the non beta version my CPU would hover around 4.95ghz now its busting through 5ghz consistently and bouncing off my set PBO overclock limit. Sim is noticeably smoother and more responsive for me with ridiculously consistent frame pacing.

When i get home this evening i will try out the certified resource hog (Ini-builds A310) doing KORD - KJFK and see if this improved performance holds up.

I must say however that i am getting concerned that the missing tiles issue is not getting the attention it needs. But ill wait .. DX 12 for me is an order of magnitude better to run on my rig than DX 11in regards to frame rates and pacing.

Edited February 22, 20233 yr by Maxis

2 hours ago, Matchstick said:

Cheers, I've just spotted the discussion on Carenado aircraft of the official forum as well.

As things stand I can now load the Sim with the Carenado C170, C337, T182, MR20 and Arrow installed, but if I then add any of the Seneca, Seminole, PC12 or Waco it CTDs on launch.

(I do also have a few of the Carenado Local Legend/Famous Flyers as well but those are all installed with seeming to cause an issue)

I have the PC12 purchased through the marketplace and it's working fine.

Sorry, bringing CoreTemp to the front seems to rob 5 or 6 frames.

Everything loaded fine for me. Not saying I have a super complicated install, but I left everything in the community folder and just rolled the dice. Looks good so far. 

1 hour ago, Krakin said:

I have some of the nastiest, jankiest, most outdatediest add-ons from flightsim.to in my community folder and so far, all of the betas I've opted into have just worked. Never bothered with touching the community folder.

I removed (unchecked in the linker) everything but GSX which is permanently linked and followed my normal routine of deleting the scenery indexes and the shader cache before I let it install. No problems at all.

31 minutes ago, Maxis said:

ICame across the PMDG parking brakes bug but managed to do the flight anyway since my default panel state has the parking brake "not set" as the default so its just being held by the chocks. I can live with that till a patch comes out.

The reason that I came back to this thread was to mention that a workaround for the parking brake issue is to start a flight with a panelstate that does not have the brake set, and simply use the set chocks option in ground services when GSX asks for brakes to be set or released. At least you can complete the flight.

Anyone find anything else wrong with the PMDGs?

Edited February 22, 20233 yr by MDFlier

7 hours ago, mrueedi said:

This is no wonder as the base sim is fixing so many ai issues:

The AI addons now need to remove the workarounds that were needed in the "broken state" again.

AIG is working fine on its own, with its own injector, it's just using AIG models + Live traffic that is causing a crash.

I haven't tested with any other AI model addons, as I don't have them installed.

2 hours ago, regis9 said:

Thanks as always to the beta early adopters for flushing out CTDs and other major issues before the rest of us (including me) jump in!

you’re welcome😂

1 minute ago, Tuskin38 said:

AIG is working fine on its own, with its own injector, it's just using AIG models + Live traffic that is causing a crash.

I haven't tested with any other AI model addons, as I don't have them installed.

I'm seeing no obvious issues so far, with FSLTL

  

6 minutes ago, HiFlyer said:

I'm seeing no obvious issues so far, with FSLTL

With FSLTL's injector or default live traffic?

Edited February 22, 20233 yr by Tuskin38

1 hour ago, Alvega said:

the WT530, but Turbomax said it is not crashing the sim too.

that's right, but I am only using the official ones from marketplace.

Edited February 22, 20233 yr by turbomax

42 minutes ago, HiFlyer said:

bringing CoreTemp to the front seems to rob 5 or 6 frames.

frame generation stops working as soon as any other window is placed ontop of the MSFS window.