02-10-2018, 03:49 AM
(02-10-2018, 12:50 AM)EverSeen Wrote: I think you will all get you p3d v4 version of FSP
But judging by the constant moaning that goes on here the v5 version will never happen. If I was dan I’d not be interested in giving a v5 version after reading this forum
We may not need a v5 ... The issue here is FSP was written in 32-bit code but P3dv4 and higher is 64-bit code. Once it's converted (if ever) it would work until a 128-bit operating system and flight sim comes out. But given how much 62-bit can handle, that also, is likely never to happen in any of our lifetimes. Even quantum computers are perfectly happy with 64-bit.
Here is a quote referring to VAS (Virtual Address Space (why most people with more than a handful of nice add-ons in FSX get OOM errors and crashes, and why we have migrated on to a 64-bit platform)):
"On Microsoft Windows 64-bit, in a process running an executable that was linked with /LARGEADDRESSAWARE:NO, the operating system artificially limits the user mode portion of the process's virtual address space to 2 GiB. This applies to both 32- and 64-bit executables. Processes running executables that were linked with the /LARGEADDRESSAWARE:YES option, which is the default for 64-bit Visual Studio 2010 and later, have access to more than 2 GiB of virtual address space: Up to 4 GiB for 32-bit executables, up to 8 TiB for 64-bit executables in Windows through Windows 8, and up to 128 TiB for 64-bit executables in Windows 8.1 and later."
Point is, all we need is a 64-bit version of FSP and we are set for the rest of our lives aside from whatever cosmetic updates Dan would like to do. But the base program will work 100%.
Most of us understand that Dan has a life outside of this pet-project, but our disappointment comes simply from a lack of communication.