Thalamus

Excuse me. But what is votrax bug ? Hard to give feedback on something I don't know what is And thank again Carny !

Thank you very much Rob !! @scoobie1 : Wob made a spreadsheet and there are some useful info in this summary page. https://vpinball.com/wiki/visual-pinball-knowledge-base/fastflip-tables-and-info/

With JP releasing Transformers Pro. Could we maybe bother you @DJRobX to put in support for tf_180 as well ?? I expect that could be a code re-use?

I'm sorry to say. I have no clue to what this is happening. But, at least now - someone else might be able to without guessing how it looks like for you

Without any picture it is quite hard to know what "missing parts" mean to you. But, for me AFM isn't 100% perfect too. So, maybe what you see is normal. Not all these *.vni projects are 100% finished.

No. I'm on a pindmd3. It used to be true that pin2dmd was required due to lack of *.vni support. That is one of the things DjRobX fixed and again led to the release of 1.7 and later of Freezy'. I have a feeling your have multiple dmddevices.dll in your system. And it finds the old one before the new. System folders maybe ?

Works perfectly here on the latest of everything. Someone forgetting to run setup.exe maybe ?

That sounds weird. I must admit, I haven't tried with 1.7.1 and the very latest sam yet. But, it worked with 1.7.0 and a few revisions back. Will try when I get home this afternoon.

change 'use Solenoid=2' to 'use Solenoid=1' in the table script and run again. Then you'll know the answer.

What specific discovery board do I need ? And where is the documentation for where to solder each pin ?

I would probably go for a lcd solution before a pin2dmd. I still haven't seen a pin2dmd with clear bright display. Also, there has been a lot of discussion and uncertainty around suppliers. Prove me wrong and I might do

https://www.dropbox.com/s/q46nj5ymrxarc2g/Thal_pindmd3_July_2018.zip?dl=0

Not sure where to report this. Running latest vpm with the new AFM and with the colored VNI. (still on 1.7.0 of freezy) . In video mode it feels just very wrong. Normally I can put up a real fight to the ufo's. It is like the dmd is behind by quite a lot. I guess I need to try out some more combinations. I'm on a pindmd3 btw. Uh: I see now that there is a color improvement for 1.7.1 of freezy. Updating. I'll report back if it is resolved. Update: So, 1.7.1 of freezy is significantly better, but I still seem to have a slight delay. Maybe it is not resolvable. Using the smart bomb (enter/plunger) if I'm in trouble doesn't help. It seems the ufo has landed already. We're not talking about huge delays here. Update2: Seems to be VNI related so probably should not be in this thread in the first place. But, well - @DJRobX might read it here. Turning off the color support and its back to normal.

Ok. My setup - has for ages been with pindmd.dll.off - meaning, disabling it. But, when I updated PBX, these files came back. It used to be that if pindmd.dll was in the folder pinballx wouldn't start at all. So when this changed ( with the update ) I didn't change any of those files. Freezy' dll didn't work for me. It requires a dmddevice.ini btw. The old lucky1 is the only one I dropped into PBX - leaving both pindmd/xdmd and xdmd-native.dll from the release version of PBX. Away from the pin right now and I'm 99% sure that is the only thing I did from 3.04 - 3.06 is for me still untested. If I use freezy' - images/videos doesn't scroll and pbx freezes on game loading. I can kill pbx and the table is actually fully loaded it is just a hung process. I'll see if I can manage to put my pbx folder up on dropbox later on. Unfortunately it will have to wait over the weekend.

You should have latest sam build in vpinmame for color roms. Its a requirement. The official doesn't support color all.