Then there's the situations where you need to pick out more than just the raw data but also a pattern of data in the same byte. Like you say, some of the data goes by faster than you can ever hope to catch by eye so your only hope is to log it and review it later. I'll agree the log file can be frustratingly long and can really bog everything down but I've found it indispensable in a few of the driver's I've been working on. This is where binary display would save me a whole bunch of time and a lot of lines in the debug window. It always seems to come down to the bit level and when there's multiple outputs in the same byte I've found it best of show each bit individually. Then I'll create 8,16,or 32 individual outputs for the bits to see which of them are involved. Compiling takes 5+ minutes so I tend to pile on a bunch of outputs in different write handlers to try and see which are firing in relation to output tests. I can't tell you how much I wish I had caught this bug a year ago or a year from now. My main machine died late last year and I've been stuck with a P4 2.something Ghz with 512Mb of RAM that I was throwing out at work everything I mentioned probably comes out of this. It isn't perfect, but it gets the job done. I have experimented with a lot of different controls to try to churn speediness out of the debug window and I keep coming back to the text box.
![tocaedit xbox 360 controller emulator not working no beeps tocaedit xbox 360 controller emulator not working no beeps](https://i.ytimg.com/vi/yWlxmTrzAaY/maxresdefault.jpg)
Just out of curiosity what are you running? You know, I started development of MH on a fairly slow machine. The debug window should give you a general idea of what is going on, but unless the game is paused, I don't think it can be trusted to give you a rock-solid, in-sync, status update. You need to keep in mind that most of these outputs fire so fast that they shouldn't be readable by the human eye at all. I just tried outrunners, and terminator 2 to make sure and aside from a little bit of flicker on term2 (it's quite literally the fastest output in mame so far) they both updated fine. If you mean lockup as in "the window turns gray and doesn't respond" then no, I've never seen that happen, but if you mean that sometimes it doesn't refresh in a timely manner or refreshes so fast that you can't see the change then I've ran across that before. I specifically use a text box because it's the quickest control to update. If you want your machine to lockup then I can add datagrid. There are built in functions in Vb to convert a number to hex, but outputtting binary numbers would require a custom function that would probably be quite cumbersome and slow.ĭatagrid DEFINATELY won't help. It might slow down the refresh speed as well.
![tocaedit xbox 360 controller emulator not working no beeps tocaedit xbox 360 controller emulator not working no beeps](https://i0.wp.com/itechviral.com/wp-content/uploads/2020/05/image.png)
I could add binary, but my guess is it would confuse the hell out of people.
#Tocaedit xbox 360 controller emulator not working no beeps drivers
Also mame drivers generally handle numbers in hex as well. Show hex is useful because if you go into a lot of the test menus for games, particularly racing games, the value of the motors are typically 0 to FF. I want to fix it, it's just that logging every change makes for a text file a mile long when you are working with strobing data and thus it turns out to be fairly useless when writing drivers. I'll either fix it or remove it next release.
![tocaedit xbox 360 controller emulator not working no beeps tocaedit xbox 360 controller emulator not working no beeps](https://www.addictivetips.com/app/uploads/2017/04/Toca-Edit-Xbox-360-Controller-Emulator-First-Screen.png)
It's completely useless for debugging, I tried to tweak it a bit, but it wasn't helpful.