forrainbow.blogg.se

Return to castle wolfenstein how to change resolution
Return to castle wolfenstein how to change resolution








I would also like to yell very loudly at the person did not allow for cut sceen skipping. If someone wants to write a bytecode compiler for arm8a or implement dynamic loading or figure out how to build a static library with gcc so that all symbols are hidden except an entry point.well let me know! Takes around 20 seconds or so to get to the title screen. That means loading the next menu or stage is slow. Ok, so note, this is a fully software, non hardware specific loading of the quake virtual machine bytecode. The SDL version does work, but i dont want to have to drag the curser around like an actual mouse, i just want to click on things. It's also very annoying how it interacts with the SDL mouse events and only uses relative motions when enabled, so my generic touch screen -> mouse events never worked right. I spent the first long while where all the fonts were totally unreadable so I had to pull the game up on my mac just to see what to click on. However arm has no such memory guarantees so I *think* my patch fixes it, it at least appears to. but the vm_interpreted was a nightmare for me to trackdown a 'simple' bug that would not exist on x86 or 64 or other strong memory machines. Lucky for me there is A) not a arm8-a encoder there and B) there is no support for dynamic loading! There is however a fully software implementation. The build system is designed to either A) use a hardware specific bytecode reader or B) dynamically link to code. The code is not pushed because the source tree is a mess and I dont feel like cleaning it up right now.










Return to castle wolfenstein how to change resolution