| Main > Software Forum |
| Sega Model 2 Emulator Full Screen Shooter fix - RamjetM2Borderless - App |
| << < (68/78) > >> |
| Howard_Casto:
Well since mine goes by the gun values and multiplies them by the screen resolution, there shouldn't be any widescreen issues. Or rather I should say all save one. If you are running the games on a 16x9 monitor, you need to run them at a 4:3 resolution if you intended to play them in the original aspect. I can put a 4:3 fix in the lua scripts, but honestly it isn't worth it. I'm almost certain that somebody is going to run into calibration issues once this is released... it's the nature of the beast unfortunately. You've got the in-game calibration. The calibration of the physical guns, and if it turns out we have issues, I'll implement calibration for the troubleshooter itself. Lightguns are a pain in the ass really. Actually, I'm sleeping fairly regularly again. Note that it's 6am here and I just got up a few minutes ago. Which is good for me, but it means things might slow down. I took a few minutes this morning and started hooking up the cfg menu for the troubleshooter. It now successfully READS all of the cfg files and also writes to the exe launch options. What's left on that end is to hook up a few misc options I haven't gotten around to yet, make a custom setup window for VON, and make a model 2 setup section, because basically m2 has to be "installed" unlike the pc games. On the internal end of things I've still got to add optional joystick support for VON, and thow my mouse code in there. The mouse code works fine, so it won't be an issue, but bugs can always arise when you are transferring code. Good luck on the proposal! |
| BadMouth:
(probably a useless post, but oh well) Regarding the issue with the windows pointer appearing: It was indeed on a widescreen(laptop stretched) to fullscreen. I don't know what the resolution was set to in M2, but it was probably a 4:3 one. Not a setup I normally play on. Sounds like you guys have a handle on it. Regarding the blue splotch following the crosshairs: makes sense. with my Act Labs guns, I pull the trigger and it puts the splotch where I aimed. It stays there until I pull the trigger again because the position isn't updated again until I pull the trigger. A side effect of using a mouse or IR gun. |
| Howard_Casto:
Found a few more minutes this afternoon. Hooked up all the VON joystick stuff save optional analog axis. I found a bug regarding having the same input hooked up to both a joystick button and keyboard key. I fixed it for von, but for the lightgun games I'll have to test this evening to see if they need fixed as well. If I can get the VON stuff and this potential bug squashed tonight, I'll add in the mouse code and start testing it tomorrow. |
| Howard_Casto:
Ok I got the VON stuff hooked up. Confirmed the bug unfortunately. It has to do with the fact that I allow joystick/mouse and keyboard inputs to work at the same time. I'll have to rework how I'm handling things a little. On a side note, after getting the von stuff working and play testing a few rounds, I have concluded that it's an awful game. I wonder why I bothered. ;) |
| BadMouth:
laser dots attached if you want to include them with the troubleshooter. Two sizes and three colors. The blue sucks, but I thought someone might insist on having blue for P2. |
| Navigation |
| Message Index |
| Next page |
| Previous page |