headkaze

Try setting keepaspect to 0 in mame.ini

What are Mame's command line options in the GameEx Setup Wizard? EDIT: Looks like Tom beat me to this one

I will have a look at the overrides. As for the trackball.. check your cfg files in Mame and that the input codes match. The input codes do work alot better now and have support for analog inputs as well. So it's improved alot since 1.95 but might require a bit of messing around since previously some things required little "hacks" to get them showing right, I'm hoping there should be less need for them in the later versions. Let me know how you go and post the usual files if you get stuck

Can you post a screenshot of a neogeo game showing the player 1 buttons like the one I've attached? It might give me a clue to what's going on. I'm pretty sure its just a mapping issue.

Did that work?

Check in your default.cfg. It doesn't still have the following does it? Because deleting default.cfg should have removed those. But if they are still there then that would explain why it's lighting the way your describing. Think about it "D" is showing correctly but A, B and C isn't. So it's like your first three buttons have been remapped like you had in your default.cfg. But you deleted that right? <port type="P1_BUTTON1"> <newseq type="standard"> KEYCODE_A </newseq> </port> <port type="P1_BUTTON2"> <newseq type="standard"> KEYCODE_B </newseq> </port> <port type="P1_BUTTON3"> <newseq type="standard"> KEYCODE_C </newseq> </port>

BTW I realised something you may also need to do which is a common problem Player 3 controls quite often mess with other mappings 1. Run Mame and press TAB go into "Input (General)" 2. Change "P3 Up", "P3 Down", "P3 Left" and "P3 Right" mappings to "None" 3. Exit Try that

You don't have to repeat the problem to me, I understand the problem your having. The thing is when I got your cfg's and tried them here, I had the same problem you were describing. I fixed that by editing the withneo.cfg file and adding in the joysticks for the neogeo entry. You still have not told me what you have tried. Go through each point I made and tell me you've tried them. Each one point by point. Write down what you've tried. Here are the main ones (again) Just because your buttons work correctly in Mame doesn't mean anything. My programs are more picky about mappings because it uses keycodes blindly. Is doesn't take into account your using a joystick or a trackball. All it does it take the keycode defaults from Mame and say where are they being remapped to? That is why for your neogeo config you had to add in your joystick inputs so it would resolve the defaults it conflicted with.

This is a perfect example of being vague. It gives me no info whatsoever. EDIT: One other thing; let's solve your PlugInLCD problem first and then worry about CPWizard. The chances are the same problem is causing them both issues anyway as they use the same input mapping code. One thing I haven't mentioned is when you change your cfg's you should exit out of CPWizard and PlugInLCD and run it again. It loads up all the cfg's when it first runs so you have to run it again when you change a file.

Support is only as good as the person your giving it to I demonstrated that it works I just think you need to double check everything. BTW I was hoping it was as simple as copying over those files I gave you but obviously it wasn't. It would also help if you gave detailed info on what you've tried to do. The more info you can give me the better help I can give back. Right now I have no idea what you've tried. Like at least if you went through all the points I've asked you to check and verified you've done them I wouldn't have to repeat myself thinking you haven't tried them. I also find screenshots and photos can help although only if they demonstrate something not apparent in the cfg's. Either way getting frustrated doesn't help anyone. It's best to stay positive and patient so you don't have the support person giving up on trying to help you. These things get solved eventually it just takes time and effort on both sides. But I tend to be less helpful to people who don't appear to be helping themselves or giving me the info I need. So far we've solved your cfg issue because you put the effort in to post the files.

Sorry Tempest I'm sure we can move onto the CFG Magician method soon enough, but I just thought it might complicate things for him, he's having enough trouble getting what I thought was quite simple working. I mean taking the cfg files and fixing them and posting them back; you can't get much better support than that! VisitorQ: In reply to your PM, I don't think you are disrespecting me at all. But I would appreciate it if you took the time to read instructions carefully. I've noticed on several occations when people lose their patience and miss a key peice of information (I know because that's what guys do; like when we purchase a piece of hardware and install it without reading the instructions). So it's worth taking the time. What I don't understand is how I can post back the working configs and it's still not working for you. Rather than putting the ball back in my court again and waiting on me to work it out for you, read over what has been said and check everything carefully.

You don't have to use any program to generate cfg's for neogeo. I just showed you a screenshot of it working on my PC using your cfg's. I even corrected them and posted them again for you. I'll repeat these few instructions just incase you skimmed over them - Make sure you delete default.cfg - Make sure mame.ini is in your Mame's root folder - Make sure the GameEx profile has ALL your button's "State" set to true (this is the one file you didn't post located in Profiles\GameEx.ini) Other than that it's probably time to do some reading because those configs work fine for me. It must be something else that is wrong. I also appreciate you trying to help Tempest but right now it's just going to complicate things. You don't need to do anything other than have a neogeo entry in the ctrlr file to do what he wants. The problem with generating cfg's is that he will have to do it everytime he updates Mame, but with a ctrlr file you set it once and that's it. Incidently VisitorQ as I mentioned before I have my button layout exactly the same and the neogeo buttons light up perfectly. The only difference is you are using different keycodes and have to have the joystick entries to avoid the mapping conflict. I'm sure you will kick yourself when you realise what is wrong but I think I've done all I can to help with your cfg files. Please read what I've written in this thread carefully and perhaps you could try doing a search on the boards (and read the PlugInLCD thread for instance). I understand there are no decent instructions which makes it difficult but the info is out there, in particular the PlugInLCD thread.

The problem was the NeoGeo config in your ctrlr file. Because you are using KEYCODE_G, KEYCODE_D and KEYCODE_F they are also mapped for Player 2's Right, Left and Down controls respectively by default. So in order to tell the plugin not to map these you should also include the joystick controls in your NeoGeo profile. As you can see from the attached pictures this is why only button 5 was lighting correctly as the rest were double mapped. Another thing is the mouse codes were wrong in the old version of the plugin so your trackball should be mapped like this MOUSECODE_1_XAXIS_NEG_SWITCH|MOUSECODE_1_XAXIS_POS_SWITCH|MOUSECODE_1_YAXIS_NEG_ SWITCH|MOUSECODE_1_YAXIS_POS_SWITCH Not with MOUSECODE_1_UP as you had it. As you can see with those changes the buttons should light correctly. I have attached the corrected ctrlr and LEDInputMap.ini files for you. files.zip

Sorry but I can't handle long posts with config files pasted in them so I deleted them. Please attach the files in the future. First thing I would do is delete your default.cfg. It has three key assignments for your first three buttons. No need to do that if your using a ctrlr file. So delete default.cfg. Next I see you have some mappings for player 4 that seem a little strange. But they are probably conflicting with your first three button assignments in LEDInputMap.ini. So I would remove these if they are not needed. P1_BUTTON1=True,LEDWiz,1,RGB,1,1,2,3,KEYCODE_A P1_BUTTON2=True,LEDWiz,1,RGB,1,4,5,6,KEYCODE_B P1_BUTTON3=True,LEDWiz,1,RGB,1,7,8,9,KEYCODE_C P4_BUTTON1=True,LEDWiz,2,RGB,1,19,20,21,KEYCODE_A P4_BUTTON2=True,LEDWiz,2,RGB,1,22,23,24,KEYCODE_B P4_BUTTON3=True,LEDWiz,2,RGB,1,26,27,28,KEYCODE_C Also you really should download the latest version of the plugin from here. I'll let Tom know he needs to update some of my plugins.

I also sent you a PM (not an e-mail). Check the link at the top of the page, it should say "x New Messages". Click on that and you should be able to read them.

Can you please zip those files up and attach them as a single zip file

Hmm why are there input codes like MOUSECODE_{0}_BUTTON1? They should be MOUSECODE_1_BUTTON1 etc. How did you enter those in? They should be selectable from the drop down list but there should be numbers not {0}?? This was a recent update I made so there could be bugs but that just seems really strange to me. I couldn't enter the codes like that?? That being said the main problem I see is your GameEx profile. You need to edit that and turn the "State" to ON for all of your buttons, that should fix that. I also have my coin and player buttons set to "Always Lit" so it's no problem to keep them that way.

Wow this post dissappeared pretty quickly. I'd appreciate it if people could help by bumping this for the next few weeks. I don't really want to pin this but I might have to if it dissapears again too soon. Damn busy boards!

I reported the popup error problem to Fyrecrypts a while ago and he said he fixed it. It should always fail silently so this should be reported to him if it's still happening. To quote him recently.. So I will make a post about it and link to this.

I have the NeoGeo entry in my ctrlr file, there shouldn't be a need to edit games manually. Remember the plugin uses input codes to map everything so make sure you have them set correctly. Also make sure the mame.ini file is located in the root of the Mame folder. Other than that it would help to see your PlugInLCD.log, PlugInLCD.ini, LEDInputMap.ini, Profiles\GameEx.ini, Profiles\MAME.ini and your mame.ini, ctlr file, cfg\default.cfg and the [rom].cfg of the game your testing it with.

You havn't downloaded the latest version correctly because you are using PlugInLCD version 2.83 yet the latest version is 2.86. Also if you don't have the Mame path correctly set then most certainly the games won't light correctly. The plugin gets it's info from the Mame executable. Check the paths in the PlugInLCD configuration under the "Options 2" tab. Make sure Exe, Cfg, Ctrlr & Ini are set correctly. Also don't just set a few LED's to test as that will most likely cause problems as well. If your still having problems please post your LEDInputMap.ini and Profiles\GameEx.ini from the PlugInLCD folder.

Here are a few things to check: - Make sure you have downloaded the latest version from the forum here. Copy the contents of the zip file into the GameEx\PLUGINS folder. - Make sure your Input Codes in the LED Input Map match those you have set in Mame - Make sure your mame.ini file is located in Mame's root folder and not in the cfg folder - Have you setup a default GameEx profile under "Profile Editor". You should at least have that one profile setup with all the buttons State's set to true and the ones you always want lit set to "Always Active". - To test the lights are working for games you should be able to select MAME from the system list in the Profile Editor and scroll through games with each game lighting it's buttons correctly. If it's not there is probably a configuration issue. - Make sure you have "Light Game Buttons in List" enabled in Options 1 Post your PlugInLCD.log and PlugInLCD.ini if your still having problems.

You probably need the Visual C++ 2008 Runtime Libraries

Yeah image lists can be funny like that. You could actually embed the images as resources and that would solve the problem. Another thing to consider would be to use array's instead of a switch block because you can use the ComboBox's selected index to index into the array. Another thing to consider is making a class where you could have all the properties of each frontend. So let's say you have a class called FrontEnd. You can have a Name, Picture, Text and Link properties. Then you have an array of FrontEnd objects. Eg. FrontEnd[] m_frontEnd = { new FrontEnd("GameEx", "GameEx.png", GameExText, "http://www.gameex.net"), ... }; Then when you recieve an item changed event in the combobox use the index of the selected item to say m_frontEnd[combobox1.SelectedIndex].Name etc.

Make the combobox DropDownStyle a DropDownList so you can't enter text into it.