HELP! Frames on Virtual DMD messed up

[LoiAbdullah]

I used to use lucky1's version of dmdext provided in this page:

It used to run great and flawless...

till I reached a dead end..

I recently updated vipnmame 3.5 to 3.6 for g-sound with latest dmdext from freezy but noticed that color files created by me aren't working properly. I tried lucky1 dmdext ver. With vpinmame 3.6 and still have problem like corruption of frame flowing. Before, I used vpinmame 3.5 with dmdext of lucky1 and it worked great, but now it works with errors in vpinmame 3.6. Errors like ignoring keyframes or delaying scenes I created by pin2dmd editor causing "color bleeding".. how can I fix this? Is the problem with setting vpinmame, dmdext or anything else I didn't come around? With vipnmame 3.6 nethier lucky1 ver. of dmdext nor freezy's works properly.

[lucky1]

I guess this is caused by these "improvements" in 3.6

- Improved DMD brightness level mapping (once more :)) for Gottlieb GTS3 & AlvinG. (always mapping to 16 instead of 4 or 5 levels, improving e.g. Waterworlds or Mystery Castles DMD fading; note that 24/25 would be optimal, but not really necessary)

- Improved DMD brightness level mapping for WPC (fixing fading e.g. in T2 and other flickering)

- Improved DMD brightness level mapping for DataEast/Whitestar, incl. 128x16/192x64 DMDs (fixing brightness levels and DMD timings, incl. video modes and the like)

[LoiAbdullah]

Got it now..

I read all of that in whatsnew.txt but didn't imagine it's gonna mess things up like this. everything in my dmd is literally "corrupted". So, what the process could be to surpass that? and excuse me for this because I'm really new to all of this