Yeah - that would be no re-mapping at all?Question so i cant play like my set up?
Button D the blue one is a mirror of button 4
so for me is red(A)- Button 1, Yellow(B) - button 2, Green(C) - Button 3 and Blue (D) - button 4
ah ok thanks good sir.Yeah - that would be no re-mapping at all?Question so i cant play like my set up?
Button D the blue one is a mirror of button 4
so for me is red(A)- Button 1, Yellow(B) - button 2, Green(C) - Button 3 and Blue (D) - button 4
SO NICE THX very much.Allright, logic was already in place - so MVS remapping galore it isdepend, in case of you decide to program both something like this could be good:
MVS Type A - NEO PAD
MVS Type B - KOF STYLE3 alternatives:MVS (classic)
MVS KOF
MVS Pad
No, that would involve a lot more - anything specific in mind?Could the remapping be exposed in the ini so that we can make a custom layout?
I was just curious.No, that would involve a lot more - anything specific in mind?
THX very much for this update. Sorry for the late, A quick test after, prelimanery result:@nonosto (and others)
Can you give this one a spin?
https://irkenlabs.com/images/jammafier-images/firmware/jammafier-2020-04-09.zip
All good?test asap.
Here you go.@adgenet -can you send me a jamdebug.txt file with the nessica issue?
Quick test all input is good. Deeper test this afternoon.All good?test asap.
In the course of trouble-shooting my MV1A I installed the excellent universal bios - http://unibios.free.fr/. Turned out my problem was that dip switch 1 was set![]()
Anyho - to access the bios menu you need to hold ABC or BCD for hw test at boot - so I implemented this. If you hold A or B button on powerup this happens:
![]()
Updated beta firmware available here:
https://irkenlabs.com/images/jammafier-images/firmware/jammafier-2020-04-11.zip
You're right! I merged in the changes from the Jvs-pac 2, it should now correctly identify g-balance IO and not misbehave if an rf-id is connected:Here you g@adgenet -can you send me a jamdebug.txt file with the nessica issue?ne is with just the Taito Nesica RFID connected by itself, and the other is with it chained through a Sega JVS IO (837-14572).
Same setup as what I talked about in the JVSPAC2 thread a while back (https://www.arcade-projects.com/forums/index.php?threads/an-improved-jvs-pac-jvs-pac-2.6972/post-150782)
Like you said in the other thread, it's mostly in the name of science since the board doesn't do anything, but the current code does seem to cause looping resets of the Jammafier. with the board connected.
My VLX Diamond contains the Jammafier, it is more versatile and functional than my Capcom with Taito official JAMMA kit.Jammafiers are so awesome im building one into Seg Dino King conversion.
Tested and confirmed!You're right! I merged in the changes from the Jvs-pac 2, it should now correctly identify g-balance IO and not misbehave if an rf-id is connected