Dynamic lights clip weirdly in both OpenGL & Direct3D 11.Cinematics and in-game HUD are stretched in widescreen.Controller input doesn't skip cutscenes.This is actually a bug in Q3A but I haven't had time to fix it yet. r_smp 1 will cause a deadlock on many systems.You'll need to connect from the console to join a game hosted by a Win8 build. Win8: Broadcast sockets are not implemented.I'm working on custom code to handle this. Menu navigation using the gamepad is almost impossible.( r_shadows 2 will do nothing right now.) Implement a shadowing solution in D3D11 to replace the missing one.Texture compression (not that it needs it).Better keyboard and gamepad UI navigation.Port the virtual machine to ARM and 圆4 so the game can run with sv_pure 1 again.The Windows 8 build is always Direct3D 11, XAudio2, XInput enabled. In the desktop version, you can actually do a side-by-side visual comparison of the two renderers. To toggle between Direct3D 11 or OpenGL you can set r_driver d3d11 or set r_driver opengl respectively. To enable or disable the gamepad, use set in_gamepad 1/0. To toggle between XAudio2 or DirectSound use set snd_driver xaudio or set snd_driver dsound. Team Arena's missionpack is not yet supported. Drop your baseq3 directory into the directory.You can find the solution for this in code\win8\Quake3Win8_VS201X.sln. This is because you're using the VM DLLs. On the command line, specify +set sv_pure 0.If launching from Visual Studio, set the Project Properties > Debugging > Working Directory to $(SolutionDir).Same goes for Team Arena's missionpack directory if applicable. Choose the relevant platform and configuration: I prefer 圆4 and Debug or Debug TA. Make sure Quake3Win32_VS201X is the Startup Project. You can find the solution for this in code\win32\Quake3Win32_VS201X.sln. You can find these under 'Debug' and 'Debug TA' (or Release respectively). See below for more information on the respective build types.īoth builds have separate build configurations for vanilla Q3A and Quake 3: Team Arena. The Windows 8 build, however, will generate a WinRT package for deployment in the Windows Store (although you can't do that unless you're Id Software). The Desktop Edition, also known as the Win32 edition, is like regular Q3A in that it runs in a window like of old. The port took me approximately three weeks in my own time and is not affiliated with my work at Microsoft and neither with Id Software, both of whom are totally unaware of this project. That's not to say it couldn't one day! One of the bonuses of this project is that I have a large platform in which to experiment with making it better/stronger/faster/shinier. Also, while it runs atop Direct3D 11, it does not contain any Direct3D 11 specific functionality that couldn't be replicated elsewhere. Those familiar with the Q3A source will not find too many surprises, but the engine could be much more efficient had it been rewritten in this way. As such it is not a complete rewrite of the original source code targeted at these technologies. The goal of this port was to bring Q3A up to latest technology while being as noninvasive as was reasonable. ini files and tinkering.This is a version of the Quake 3: Arena source code built for 圆4 & ARM, Windows 8 and Windows Desktop, Direct3D 11, XAudio2 and XInput. It will probably be stretched on a newer monitor but at least you can view the videos.ĭon't know about UT or Stronghold Crusader, but I know UT is from the same era as Quake 3 where 320x200, 640x480, and 800圆00 were common resolutions. If you want to watch those use this resolution instead: Be aware that the cinematic videos will NOT be visible at a non-4:3 screen resolution. If your native res is different, set the width and height to whatever. The r_mode "-1" enables custom resolution specified by the other two statements.ĭouble-click the Quake3.exe icon in the parent folder and it will start with that resolution. If you know where your Quake3 folder is (or just do a search for Quake3.exe) you can go into your baseq3 folder and manually edit the q3config.cfg and make sure you have the following variables set If you're running Windows 10 it may not like the default resolution. It runs just fine for me on Windows 7 64-bit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |