April 7, 201511 yr Author Wes left a few months ago, before 2.5 was released ... primarily to be closer to his family. Adam has picked up where Wes left off ... there are few more new faces I've communicated with on P3D development team (so I'm assuming they have increased in size or where there all along). I'm assuming John V. wasn't aware as he probably wouldn't have posted his comments about no P3D 64bit and his meeting with Wes back in Nov 2014 if he had known Wes was no longer with LM. As far as P3D goes, business as usual for v3 and beyond. There really is nothing to see here as this news is old news. Cheers, Rob. Well I'm pretty happy with the current direction so no change is good news Best wishes to Wes for the future, thanks for taking us this far on the journey! You can probably lock this one now Rob.... Cheers K Kevin Firth - AMD 9800X3D; Asus Prime X670E; 64Gb Cas30 6000 DDR5; RTX5090; AutoFPS
April 8, 201511 yr Three cheers for Wes Bard!!! Long Live Wes Bard!!! Disclaimer: [email protected] on Asus Maximus X Formula, G.Skill TridentZ RGB 4x8GB 4266/17 XMP, EVGA 2080 ti Kingpin (8400/2160Mhz), Samsung 960 EVO 250GB PCIe M.2 NVMe SSD , 28TB HDD total - 4TB+ photoscenery, Romex Software PrimoCache RAM and SSD cache (must have!), 3x1080p 30" monitors, Samsung Odyssey VR HMD, Pimax 4k & BE HMDs, Samsung Gear VR '17, Homdio v1, Cardboard, custom loop 2x 360x64ML Rads, Thermaltake View 71, VRM watercool, Thermal Grizzly Conductonaut CPU (naked die), Fujipoly / ModRight Ultra Extreme System Builder Thermal Pad on MB VRM. 8x Corsair ML120 (slight positive pressure). 🙂
April 8, 201511 yr As far as 63 bit goes, the present state of the art at 32 bit can still be quite awesome, albeit for the slight lack of memory at the end of a flight usually when the destination airport detail is loading in, and that finalizing as the touchdown point gets nearest, and alas, the dreaded OOM. With some more refinements, it should be just possible to overcome this hurdle, me thinks.
Create an account or sign in to comment