Main > Software Forum
Johnny5 Run-time Error
Howard_Casto:
Heh, don't erase is the name of the directory I keep all my source code in, I didn't mean for you not to erase it, it's a reminder to me. ;)
This should be obvious, but that path does match where you actually have j5 installed doesn't it?
The script is designed to self-exit when you press esc, so that is normal operation.
As I said, the garbled graphics thing is soley because of mame. There is absolutely nothing you can do about it. The only reason it doesn't corrupt when you exit out of j5 via esc is because then the screens aren't swapped, rather mame moves itself (which I can't do unfortunately) so it doesn't have those issues. As I said, aaron's upcoming changes will fix that.
The delay isn't related at all. It usually depends upon how well your system can handle haveing two instances of mame running at once. Mame is called by j5 to get vital info. I have no clue why, but some systems seem to have a problem with that. Mame is very tiny when you don't launch a game, so I have no clue why.
Also the ahk tag in the script controls a delay on an old-school vb timer, which are notoriously resource dependant. Having hi-priority in mame set might cause the timer to run slowly. In any extent.....
You can try adjusting the "-ahk " delay to a smaller number to increase speed, but it may cause dislay errors in j5. You have to kind of tweak it for each system. I made it high purposefully so it would always display right.
On a different note, how did the pause syncing work for you? I've had much more luck with this script but I always like to get fedback from others.
Dustin Mustangs:
Lol, that is pretty funny. I can't imagine I am the only one who will make that mistake.
The path does match where I have Johnny5.exe.
I'll try messing with that delay. It would be weird if it's my machine that is so slow with this. I just reinstalled windows and only put mame related apps on it other then NAV and the whole slew of windows updates. Needless to say it doesn't have much bogging it down.
It got out of sync on me once, although I really haven't had a chance to use it much other then just testing while trying to get it set up correctly. I'm pretty sure it was my fault anyways due to me getting ancy during that 14 second wait and hitting p again before it had a chance to display but I am not sure. If I can't get this delay down I think I am going to have to go with one of the other options for displaying controls. If I have a hard time waiting for it to come up then I can only imagine all the problems it will cause when someone else is behind the controls and starts randomly pushing buttons while they wait. I am still optimistic but I feel the options are running short. *knocks on wood*
Dustin Mustangs:
The delay settings had no effect except would make the script not work at all if I went too low.
The resolution in mame ini was switched from auto to 800x600, my desktop res. I imagine Johnny's resolution and Mamewah's resolution are set dependant on their layout files which are both at 800x600 also. This had little to no effect.
I did notice something weird and possibly realted though. With mame running 1942 it takes up 14% of my cpu resources. If I pause it that shoots up to and stays at 99% until I unpause at which time it returns to normal. This is regardless of how I launch mame and if the script is running or not. That doesn't seem right, does it?
:dizzy:
Howard_Casto:
No... they aren't...
mamewah has resolution settings (not familair with it so i don't know where specifically)
to set the "resolution" in j5 you launch it with the -position tag (read your readme.txt)
It sounds to me like you has rdtsc(spelling?) timing turned on or high priority turned on in mame. If not your issue is operating system related. I know it's not a fault of mame and as you said, this is occuring if you have j5 running or not.
Dustin Mustangs:
I checked both the rdtsc and the high priority settings in my mame.ini and they were both disabled. I tried changing them anyways and it didn't help any regardless of how I had them set.
I didn't get a chance to verify all the resolution settings but I will give it a go tonight although I doubt it will solve my problem.
Could you possibly elaborate on your 'operating system related' thought??
I am starting to loose hope which sucks because I REALLY wanted to make use of this app.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version