Due to heavy spamming attempts on this forum, automatic registration has been disabled. We will approve registration requests as quickly as possible (unless you're a spammer of course )
Started by David, February 21, 2018, 01:28:01 PM
Quote from: TrainzLuvr on February 24, 2018, 01:21:29 AMIs this some kind of a "hip" thing you need to do because everyone is doing it lately, or is there a valid reason to go 64-bit only for a killer feature that no other MRR planning software has, and it desperately needs 64-bit functionality?Does AR need more than 4GB (3.5GB) of memory to warrant switching to 64-bit only?Your 3D viewer should rely more on the graphics chip memory and advanced functionality there (if computation is needed such as CUDA, OpenCL...or OpenGL/DX/Vulkan) than CPU memory. Even the Intel IG is nowadays fast enough that one should never let the CPU do any graphics tasks.Screen resolution is irrelevant to application's bit-ness and is driven by the underlining OS. Matter a fact AR should be resolution independent in every aspect.I'm telling you this because if you keep being stuck in the Windows land, you will remain there. The world will move to more sleeker and leaner ARM architectures running on tablets with 10-16" screens, or even a pair of glasses, having about the same power as an i5 or i7 CPU today.If anything, I would focus on liberating AR from the Windows shackles and making it as much OS agnostic as possible.Just my 2c.