Most effective method for identifying system requirements involves thorough analysis and stakeholder input.
Most effective method for identifying system requirements involves thorough analysis and stakeholder input.
The main issue I'm encountering is the absence of a starting point for baseline hardware requirements. It seems like a poor approach to design an app based solely on your current development setup and then hope for optimal performance later. Instead, establish clear hardware and software standards first, then adapt your application accordingly. You shouldn't create the app and then test its compatibility; rather, define your goals and build around them. With such delays, the safest strategy is to start with the lowest feasible specs you believe will function, gradually adjusting between them until you locate a suitable combination. Note that GPU passthrough isn't available on Windows, except for enterprise versions.
Yurizaki is a genuine developer, so I fully understand the comments. Given this might be your very first project, you should be okay with mentioning dual-core CPU, ample RAM, a 3D graphics card, and disk size being manageable. If it's your debut, most people probably won't play it (sorry!), but if they do, they should be able to run it. Shouldn't be an issue if they can't, likely because the machine struggles with Microsoft Word too.