Software Support > GroovyMAME
Lightgun flasher over groovymame in fullscreen
phasermaniac:
Mmmm, testing with Zombieraid, it works perfect for p1, but not for p2 (on dark zones it shoots and release)
Also it doesn't seem to work if no lag is applied, although for the moment I have not tested any game that needs "Guncode offscreen" with no "frames to apply button".
On another hand, I find the plugin a little confusing to use, and I think it will for other users. What do you think about
Simplifying:
- Guncode off-screen: Instead of "yes" why not input here the input deseired? this way you wouldn't have to create another gunlight button.
- Frames to apply gain: I would change to "flash length" and add a -1 value to be "until release" so you can eliminate "Gain method"
- Only with gain: I would change that for "Input lenght", to give the freedom to set a frame number, or -1 to be "until release", so it would have the same logic that "flash length"
Renaming and reordering, I think this would be easier to understand:
Action P1 Fire
Offscreen Action P1 Reload
Input Gun Button 1
Input Length 3
Input Delay 2
Flash Length 4
Flash Brightness 0,5
Flash Contrast 0
Flash Gamma 0
Also I think, that would be good to keep the same names in the mame menu and in the config game files in "gunlight" directory.
Another thing I feel weird is that when you update your gunlight config, the order of variables change in the config file. Would be nice to be always the same order, as if you want to modify or compare some files it can be very confusing.
Sorry to be this long. All this are ideas which I think would help in the ease of use.
phasermaniac:
Ok, tested a little more and I think what is the problem with p2:
For offscreen reload p2 is looking at p1 coords, so if you are pointing p1 at screen, p2 shoots ok, else p2 shoots ans reloads at once.
Rion:
--- Quote from: phasermaniac on November 15, 2022, 02:01:19 pm ---Mmmm, testing with Zombieraid, it works perfect for p1, but not for p2 (on dark zones it shoots and release)
Also it doesn't seem to work if no lag is applied, although for the moment I have not tested any game that needs "Guncode offscreen" with no "frames to apply button".
On another hand, I find the plugin a little confusing to use, and I think it will for other users. What do you think about
Simplifying:
- Guncode off-screen: Instead of "yes" why not input here the input deseired? this way you wouldn't have to create another gunlight button.
- Frames to apply gain: I would change to "flash length" and add a -1 value to be "until release" so you can eliminate "Gain method"
- Only with gain: I would change that for "Input lenght", to give the freedom to set a frame number, or -1 to be "until release", so it would have the same logic that "flash length"
Renaming and reordering, I think this would be easier to understand:
Action P1 Fire
Offscreen Action P1 Reload
Input Gun Button 1
Input Length 3
Input Delay 2
Flash Length 4
Flash Brightness 0,5
Flash Contrast 0
Flash Gamma 0
Also I think, that would be good to keep the same names in the mame menu and in the config game files in "gunlight" directory.
Another thing I feel weird is that when you update your gunlight config, the order of variables change in the config file. Would be nice to be always the same order, as if you want to modify or compare some files it can be very confusing.
Sorry to be this long. All this are ideas which I think would help in the ease of use.
--- End quote ---
I second the renaming and reordering. Good idea :)
phasermaniac:
Hi! I have been trying to solve the offsceen reload problem, something like:
--- Code: ---if port == 1
local guncode_xaxis = manager.machine.input:code_from_token("GUNCODE_1_XAXIS")
local guncode_yaxis = manager.machine.input:code_from_token("GUNCODE_1_YAXIS")
end
if port == 2
local guncode_xaxis = manager.machine.input:code_from_token("GUNCODE_2_XAXIS")
local guncode_yaxis = manager.machine.input:code_from_token("GUNCODE_2_YAXIS")
end
--- End code ---
or better
--- Code: ---local guncode_xaxis = manager.machine.input:code_from_token("GUNCODE_"port"_XAXIS")
local guncode_yaxis = manager.machine.input:code_from_token("GUNCODE_"port"_YAXIS")
--- End code ---
but I don't know how to use the variable port and whats its actual value, any advise? thanks
psakhis:
I need to do some refactor to detect p2 buttons
I will do it on the next days.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version