The NEW Build Your Own Arcade Controls
Front End Support => MaLa Frontend => Topic started by: mike boss on July 14, 2012, 12:02:06 pm
-
I'm working on a layout and all of a sudden I'm getting the following error.
Never had this issue before when using MaLa.
Any help ?
Access violation at address 00487DA5 in module 'MalaLayout.etc'. Read of address 03280000.
-
Don't have an answer, but I've gotten the same, or extremely similar error. Sometimes repeatedly when trying to make changes and save a layout.
So yours is not an isolated case.
-
I've re-booted and even tried with another layout and got the same results.
Quite a pain in the ass really.
-
Deleted the folder, reinstalled MaLa, issue persists.
-
Any help ?
-
I'm thinking this could be an issue with the files ?
I've tried my other PC and the same issue.
This is odd !
-
.
-
I got the error when I was messing around with animations, video on both horizontal and vertical in the same layout file.
It did allow me to save my progress even after getting the error.
It's been a while since I messed with the offending layout, but I just tried it again and aren't getting any errors.
I had apparently deleted the animations, but still had video and video 2.
Try getting rid of some of the less main-stream elements and see if the problem goes away.
I'm thinking that I had odd sized images for the animations or something....or was using the horizontal ones on the vertical version or something....
or maybe just a memory thing that has gone away because the memory has been filled up with other things.
I just a dumb end-user :dunno
-
I had the background and then 3 custom elements, games list, snap and video.
All files were PNG as the transperancy works better.
Anyway I resaved the images and tried again and it worked.
Odd !
I knew it was something when the error was the same on 2 different PC's.
None the less, save the files again, change the names and it worked.
I've now completed two more custom layouts ! LOL
-
I got this error when using PNG-24's as my background image - on two different machines.
I resaved my backgrounds as PNG-8's and the problem went away. Might have just been a coincidence but the error didn't return.
-
I'll need to look again @ the PNG files I was using.
I'm glad I was able to get it resolved.
It was driving me nutts !