Marty2JKA Posted November 8, 2014 Posted November 8, 2014 Hello, Why is the Config redirected to C:\%user%\Documents ? I dont play in a Domain/ Network Enviroment.Exists a Commandline switch to avoid to save the Config in C:\%user%\Documents\OpenJK. Personally i hate this that all config saves go C:\Users\>different places< from hundred of games. Bug(s)!If i in windowed mode and change the Customheight and -width in the Console from 4:3 (1280x768) to 16:9 (1920x1080) and return this with vid_restart: OpenJK crashtThere a always show white loading Screens in 16:9 format and the Videos are stretched in 16:9. The 2D Objects (Crosshair, Ammo etc..) are stretched in 16:9. sad this is always not fixed.If i type in the console a '2' or '8' with numpad/numblock it clears the actual line. Is this really a stable Replacement for JKA or should i use the Original version 1.01 from Raven?
eezstreet Posted November 9, 2014 Posted November 9, 2014 1. It's done that way to prevent issues on launch when not running as administrator. If you would like to change this, add this to the commanfline:+set fs_homepath "Your directory here" 2. This is an issue with the original game and requires editing of the files, which goes beyond the scope of OpenJK. 3. Try with munlock off? Could be a hardware issue on your end. Either way, it wouldn't make the line "disappear," rather it's acting as an arrow up/arrow down signal. In many ways the OpenJK console is improved; some of the new features include scrolling with the scroll wheel and proper tab completion (including tab completion with devmap).
Marty2JKA Posted November 9, 2014 Author Posted November 9, 2014 Thanks for the Replay 1. huh, , great. I don install my games on C:\Programs. Because the Right Management System. Set fs_homepath .\ works 2. Which files ? 3. I tried with numlock off and on. I think is a VK_numpad2 and VK_numpad8 vs VK_Up / VK_Down api thingI'm not a Coder. .I dont see a VK_NUMPAD8/2 detail in the Source. Could try: switch(wParam) { case VK_NUMPAD2 break; case VK_NUMPAD8 break; case VK_UP // scroll up: arrow-up case VK_DOWN // scroll up: arrow-up }
ensiform Posted November 9, 2014 Posted November 9, 2014 The numpad keys seems to be a bug in SP. I assume it happened in base as well, we haven't changed any of the keys code there. Brought over the change from MP.https://github.com/JACoders/OpenJK/commit/e04792c33b0b206932c5ac01c4f80befb3d5995e I don't get crashes when changing the resolution at the main menu via console? You should probably avoid using vid_restart when running the game due to the separated renderer module can cause issues like that still.The white screen is unlikely to go away, we fixed every other case of it but it just doesn't go away. Cinematics and 2d are actually drawn at 640x480. And rendered at your resolution. Requires changes to mod code for 2d, cinematics were adjusted to be that way on purpose.
Marty2JKA Posted November 11, 2014 Author Posted November 11, 2014 I Used the windows version 1.0.1.0 from JK Build BotSo, I Create a VM with Windows 7 Home, Visual Studio 2010, GitHUB und Cmake and Compile OpenJK Successfull. Now it runs very fine and the Keyboard Bug is gone. Is now Version 1.0.1.1
ensiform Posted November 11, 2014 Posted November 11, 2014 The console keyboard thing wasn't really a bug, more like oversight on Raven's part of not allowing you to use numpad keys as numbers.
Xycaleth Posted November 11, 2014 Posted November 11, 2014 The console keyboard thing wasn't really a bug, more like oversight on Raven's part of not allowing you to use numpad keys as numbers. Numpad worked without any problems in JK2. They borked it in JKA some how.
ensiform Posted November 12, 2014 Posted November 12, 2014 Numpad worked without any problems in JK2. They borked it in JKA some how.Even in JK2 SP?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now