July 21Jul 21 11 hours ago, DAD said:I am on SU6 beta and cannot expect it to work so no complaint. I'm on SU6 beta too, 737-700 amd 777 working after both being uninstalled / installed through OC3. Edited July 21Jul 21 by jcomm Learning to fly gliders since 1980AMD Ryzen 5600x, 32GB DDR4, RTX 3060Ti (8GB), GIGABYTE B550 AORUS Elite AX V2 mobo, 1TB + 500GB nvme m.2 disks
July 21Jul 21 yep its not not 737 with WASM issues i have been having issues last 3 hours and i fly FENIX , going through re installing apps and scenery ROG Crossair Hero X670e , 9900X, TUF 4090 , X4 NVME's. OS 2TB 980 Pro , MSFS 2TB WD Black , Kington Fury 64GB ram ( 6000) Corsair RM1000 PSU, Artic Freezer iii 360 AIO . Phanteks P600s Case ,TCL QM8B 50" 120 Hz TV,second 24 inch screen for charts you tube etc, and 11" touch screen for the EFB. Warthog Stick and TCA Captains throttle ( full pack) Velocity 1 Rudder Pedals , extreme3D for the Tiller,Streamdeck XL x2 / Streamdeck +/Streamdeck mini because i like pressing buttons
July 23Jul 23 Author So, updated the planes again since PMDG put out the fix for the WASM crashes, however once I enter my data for the performance in the PEF INIT tab on the flight computer and press enter, the red boxes and the WASM crash is back at least for the 700 series Asus Tuf Gaming Plus B550 - Ryzen 7 5800X3D - Asus GeForce 4080 RTX OC Edition - 64GB DDR4 (3600Mhz) - EVGA 850W Power Supply - 2X 1 TB NVME PCIE gen 4 - Windows 11 (25H2)
July 23Jul 23 I had a WASM crash in the 777 current version. No red screens but all knobs and buttons were frozen. Removed a custom panel state and now all is good.side note, I wish there was a proper “on GPU” panel state included, then I wouldn’t need to create my own. Dave Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU
July 23Jul 23 I just read that what i thought was a WASM crash seems to be a SU5.1 issue. Let the plane sit for 5 to 10 minutes after entering the Cockpit. Will give it a try.Michael Moe Edited July 23Jul 23 by Michael Moe Michael Moe
July 23Jul 23 44 minutes ago, Michael Moe said:I just read that what i thought was a WASM crash seems to be a SU5.1 issue. Let the plane sit for 5 to 10 minutes after entering the Cockpit. Will give it a try.Michael MoeAnd it worked hereMichael Moe Edited July 23Jul 23 by Michael Moe Michael Moe
July 24Jul 24 7 hours ago, Michael Moe said:I just read that what i thought was a WASM crash seems to be a SU5.1 issue. Let the plane sit for 5 to 10 minutes after entering the Cockpit. Will give it a try.Michael MoeI got the WASM crash during 1st flight of 738 since updating to the supposed WASM fix update - occurred on rollout after landing. Previously on all other versions since the 738 original release I had exactly a single WASM crash. i7-6700k • Gigabyte GA-Z170X-UD5 • 32GB DDR4 2666 • EVGA FTW ULTRA RTX3080 12GB
July 24Jul 24 There is a new 737 update - at least for my 800 - in OC3:This is build 4.0.59.This build continues the effort to increase stability throughout the aircraft code files, with specific fixes for:PERF INIT freeze on certain panel state loadsPanel state load refinements for CDU pages Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
Create an account or sign in to comment