/vr/ - Retro Games

>>4942525
>>4942508
>>4942494
>>4942461
>>4942548
>>4942536
Also based on what the other dude said about footprint I would suggest since you're interested more in retro stuff that you go with graphical options based on DirectX instead of opengl. There's been a yuge stink going on in gzdoom regarding graf's switch to opengl exclusive (you need oGL 2.0 just to fucking RUN software mode, just to make it look like it did in 2001 you need to have shit that can run UT 3).

Its easy to miss the fact that opengl is very inflexible on the user's end, its something you either have the minimum requirements for or not, there is no way to get around emulating it or shutting off options that you dont need. OpenGL is evil and it shouldn't have ever left the Workstation environment where it came from.
> also dont use shaders, make them optional, instead get similar effects with texturing and lighting

=====
=====

Also if you "barely" know programming, even if you consider yourself a fast learner, this is NOT FOR YOU. Go make mods for the next 3-5 years for these games using programming then go for the gold.
> This is something that will take you a long time even if you're dead proficient at it.
> in terms of Mapping, totally unrelated to the programming aspect, rich high quality megawads like BTSX, DOTB have taken years with a team of mappers
You will not succeed trying to copy/paste and jury rig stuff together based on tutorials, you have to know what you're doing and even then it will take 3 years for you to finish your game.
> just speaking in realistic terms here
There are times where youll hit very serious problems that you cant identify or figure out how to fix even with a really hacky solution, they will take a long time to solve, and it will contribute to dissipating your muster to keep going. In the end it will be anothr failed project website with dead links that people cant even download the source code for
> dont-be-that-guy.jpg
Pic related, You need more science skill