September 2, 20205 yr Commercial Member 1 hour ago, ChaoticBeauty said: It was mentioned in another thread that AMD's software does not recognise the simulator anymore because the executable's name was changed. Should be an easy fix for the next driver update, but perhaps Asobo should consider making its name consistent to prevent this from breaking with every single client update. The executable name hasn't changed, it's still called Flightsimulator.exe, it's the *folder* name that has changed, because like any other Windows App from the MS Store, the folder name contains the version number. This looks to me very shortsighted by AMD: if they need to recognize if MSFS is running, they can just call the proper Windows API to get the ProcessName, which can be obtained without a complete path, and if they stored somewhere the complete pathname, they are going to have problems with each and every game in the WindowsApps folder ( basically, everything on PC Gamepass ) each time they are updated. So no, it seems to me it's entirely AMD's fault here. Edited September 2, 20205 yr by virtuali Umberto Colapicchioni http://www.fsdreamteam.com FSDT on Facebook
September 2, 20205 yr You know he had bad judgement the day he bought an AMD GPU....:-P https://fsprocedures.com Your home for all flight simulator related checklist.
September 2, 20205 yr 23 minutes ago, Bosco19 said: Get a grip people. It isn’t like enduring a pandemic. Yes it is - it is Flight Simulation and it will go on and on and on... Also I would go with a better title like "The Patch Broke My Install". Regards bs Edited September 2, 20205 yr by bean_sprout AMD RYZEN 9 5900X 12 CORE CPU - ZOTAC RTX 3060Ti GPU - NZXT H510i ELITE CASE - EVO M.2 970 500GB DRIVE - 32GB XTREEM 4000 MEM - XPG GOLD 80+ 650 WATT PS - NZXT 280 HYBRID COOLER
September 2, 20205 yr 9 minutes ago, fogboundturtle said: You know he had bad judgement the day he bought an AMD GPU....:-P I have the same problem, and my GPU is an RTX 2080.
September 2, 20205 yr 49 minutes ago, w6kd said: All right guys, give the guy a break--he does have a legit issue--a forced update from M$ broke his previously-working configuration, and they've provided him no way to get back to his working config. You just might find yourself in a pretty cranky state if it happened to you. Yikes! 'M$'... From an Admin? I thought even anti-microsoft people stopped using M$ years ago. 😄 Rob (but call me Bob or Rob, I don't mind). I like to trick airline passengers into thinking I have my own swimming pool in my back yard by painting a large blue rectangle on my patio. Intel 14900K in a Z790 motherboard with water cooling, RTX 4080, 32 GB 6000 CL30 DDR5 RAM, W11 and MSFS on Samsung 980 Pro NVME SSD's. Core Isolation Off, Game Mode Off.
September 2, 20205 yr Author 28 minutes ago, virtuali said: The executable name hasn't changed, it's still called Flightsimulator.exe, it's the *folder* name that has changed, because like any other Windows App from the MS Store, the folder name contains the version number. This looks to me very shortsighted by AMD: if they need to recognize if MSFS is running, they can just call the proper Windows API to get the ProcessName, which can be obtained without a complete path, and if they stored somewhere the complete pathname, they are going to have problems with each and every game in the WindowsApps folder ( basically, everything on PC Gamepass ) each time they are updated. So no, it seems to me it's entirely AMD's fault here. That fortunately was resolved 3 days after release. It recognizes it now. That's what this update wiped out. Luckily the driver redo fixed it.
September 2, 20205 yr 2 hours ago, fogboundturtle said: You know he had bad judgement the day he bought an AMD GPU....:-P Yep. AMD/ Radeon cards have always had driver issues. Look at almost any new game forum, and people having graphical issues, and it almost always comes down to AMD. I've never had a problem with an NVidia card. So yes, I'm a word not allowed. 😜
September 3, 20205 yr 2 hours ago, Bosco19 said: LOL! People act as though they had to get financing to buy this title. I can fit a hundred bucks worth of groceries into one bag these days - and it’s gone in less than a week! That's what happens to me when I buy those Chewy Chips Ahoy FAMILY SIZE. Anyway, glad the OP found the problem but he needs to report it to MS/Asobo so that their updates perhaps go a bit more smoothly in the future, if that's possible. Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
September 3, 20205 yr As this is now resolved with the solution listed, would it be more useful to rename the title something like 'Lost 3-screen support after update' rather than the current emotive title that isn't helpful to anyone? Particularly as this wasn't totally MS/Asobo's fault. We can leave the 'M$' references in for Asobo to have a laugh at! 😄 Rob (but call me Bob or Rob, I don't mind). I like to trick airline passengers into thinking I have my own swimming pool in my back yard by painting a large blue rectangle on my patio. Intel 14900K in a Z790 motherboard with water cooling, RTX 4080, 32 GB 6000 CL30 DDR5 RAM, W11 and MSFS on Samsung 980 Pro NVME SSD's. Core Isolation Off, Game Mode Off.
September 3, 20205 yr 15 hours ago, DarkMantle said: So mine was working perfectly. Especially after the Radeon update. Had support for 3 monitors and it was running great. The mandatory update ruined it all. How do I get my money back? If that's how short your fuse to solve an issue is, you are in the wrong hobby
Archived
This topic is now archived and is closed to further replies.