March 11, 20224 yr Author 1 hour ago, bobcat999 said: I hope they look at loading times - that is now the biggest bugbear of mine at the moment. They said in the latest Q&A that: Sim Update 9 will reduce the amount of time required for the initialisation process (the minute-long pause between pressing the icon and the application booting). The package scanning process (the loading after the "Checking for updates" phase) would require a deep architectural rewrite in order to become faster, but it is something that the entire team would want to see changed in the future.
March 11, 20224 yr 24 minutes ago, ChaoticBeauty said: The package scanning process (the loading after the "Checking for updates" phase) would require a deep architectural rewrite in order to become faster, but it is something that the entire team would want to see changed in the future. Which begs the question "Why was it written that way in the first place if it appears it can be fixed? 1) Did they not realise it would cause such a delay entering the sim? 2) Did they not think anyone would be bothered by it? 3) Is this another downside to the sim appearing to have been rushed to market before it was really ready? OS: Win11 Home; Mobo: Asus TUF Gaming Z690-Plus WiFi D4; CPU: Intel i5-12400 (Alder Lake) 4.4 GHzRAM: Corsair Vengeance DDR4 64Gb (4x16GB) 3600 MHz; GPU: MSI Radeon RX 5700XT [8GB] SSD: Corsair Force MP510 (for OS); 2x 1TB & 1x 2TB Sabrent Rocket Nvme PCIe 4.0 (one for sim, two for addons)HDD: Seagate 3TB (Data); Seagate 1TB (Programs), ASUS TUF Gaming VG32VQ1B Curved 31.5" monitor, 1440p, 38Mbs ethernet Fulcrum One Yoke, Honeycomb Bravo throttle, Thrustmaster Airbus TCA sidestick & throttle, Logitech Pro pedals, Xbox wireless gamepad (1st gen)
March 11, 20224 yr Author 1 minute ago, 109Sqn said: Which begs the question "Why was it written that way in the first place if it appears it can be fixed? The issue is attributed to legacy FSX code. You can find a more detailed explanation about that in the official summary of the last Q&A. Quote Martial - I was talking previously about FSX inheritance. So, the system we are currently having is reading all the applications, all the information needed to display on the main menu. Even if it’s planes or airports or anything else, it’s there. When you’ve got plenty of these items, it takes time to parse and read this information. That’s an issue we are well aware of. The solution would be to create a new system that puts the information outside of the main title. But in the same way, we’ve got to make that compliant with the former packages. It’s not that simple. Also, we’ve got a team dedicated to package delivery. They are thinking about creating a new system that would be compliant with the follow-on that sorts information in order to be faster when we are loading them. Jorg - We all agree this has to change. But I think what Martial is saying is it’s a pretty deep architectural change. It’s going to take us a while. But, there is not a person on the team that doesn’t want this to go faster. It’s just, we can’t commit to a date. Considering that MSFS takes up at least 10x more disk space than FSX that explanation makes sense. There is no doubt that it was rushed to the market somewhat, but replacing legacy FSX code has been an ongoing process since early development which will continue for years to come, so if we had to wait for that to be completed we likely wouldn't even know that it's in development today.
March 11, 20224 yr cloud gaming and multiple screens coming, finally we can connect all our various cell phones and have surround gaming, finally. YEAH 😀 AMD 7800X3D, Windows 11, Gigabyte X670 AORUS Elite AX Motherboard, 64GB DDR5 G.SKILL Trident Z5 NEO RGB (AMD Expo), RTX 4090, Samsung 980 PRO M.2 NVMe SSD 2 TB PCIe 4.0, Samsung 980 PRO M.2 NVMe SSD 1 TB PCIe 4.0, 4K resolution 50" TV @60Hz, VR: Pimax Crystal Light + HP Reverb G2 @ 90 Hz, Honeycomb Bravo Throttle Quadrant, be quiet 1000W PSU, Noctua NH-U12S chromax.black air cooler. 60-130 fps. no CPU overclocking. very nice.
Archived
This topic is now archived and is closed to further replies.