Jump to content

Recommended Posts

  • Content Provider
Posted
3 minutes ago, Westworld said:

> Can you test with the builds linked in the top post, please? This should have been fixed.

 

those named: Installer\Builds\dmdext-2.1.2.7-x86-Release.zip

 

I wondered because 2.1.2.7 or do I need to use the .msi ones?

 

There's also the nice new "About" buttons we can right-click on now.

 

@freezy Does the About button version get updated each time?

 

image.thumb.png.669d77947aa997f13087d7344cb32106.png

 

 

  • Content Provider
Posted
Just now, freezy said:

 

Yes, it's automatic.

 

Nice. Also... would it be possible at some point to add a CLOSE DMDext button when right clicking? It just makes it easier to close out in a cabinet setup, if for whatever reason it didnt close out on its own.... and we needed to close it (without needing to use Task Manager, or look for it on the taskbar, assuming its not hidden) etc.

Posted
2 minutes ago, TerryRed said:

Also... would it be possible at some point to add a CLOSE DMDext button when right clicking?

 

If you give me a use case that is not "let's fix the symptom instead of the problem", sure. ;)

Rather on GitHub though, since that's not something related to this release.

  • Content Provider
Posted
2 minutes ago, freezy said:

 

If you give me a use case that is not "let's fix the symptom instead of the problem", sure. ;)

Rather on GitHub though, since that's not something related to this release.

 

More for testing than anything... but yes I ideally it should be closing on its own.

Posted

oops, sorry, I missed that.

I confirm that they fix the issue, both 32+64 bit versions work fine (so far I tested setup, tomorrow I'll play some tables)

many thanks!

Posted
1 minute ago, Westworld said:

I confirm that they fix the issue, both 32+64 bit versions work fine (so far I tested setup, tomorrow I'll play some tables)

many thanks!

 

Awesome, thanks!

  • Administrators
Posted
On 6/29/2023 at 3:23 AM, lucky1 said:

 

Until there are open issues with your build it makes no sense to me make a public release.

From the plugin side the main issue remains that you manipulate the data coming  from pinmame

instead of just forwarding it like it is. What is the reason for this ?

To make things easy I used the same API calls for the plugin as for the pinmame dmddevice API.

Why make things unnecessarily complicated now ?

 

@lucky1 So what is your primary hangup?  Why are you holding back everyone from being able to move this hobby forward? 

 

Freezy has my 100% trust in what he has been able to do and in everything he has been doing for this hobby and community.  I think he's done very well to work within your demands for getting this plugin going.  I believe that his intentions are genuine and best for the community. 

 

For the love of the community... Can we please get this over with and move forward?

Posted (edited)
On 6/30/2023 at 8:26 AM, freezy said:

 

Do you have a DmdDevice.log with the crash?

 

 

Tested this morning more. And it doesn't crash . Log(s) shows it is initialize correctly, but I don't get anything on the display. 
using 2.1.2 dll, it is working directly (attached DMDdevice.log + log.txt are from the PinballX run).

I understand that PinballX is out of scope for you, but any hints/tips or tricks to get it to work would be appreciated (so maybe Tom can implement this and can get it to work)?
If not, I'm OK with it is as well and I will look for other workarounds.

Anyway. Good work on this and hope we will soon see something for VPE for end-users

 

EDIT: Not sure if this is for you or FLEXDMD creator.
Launching FLEXDMD gui (to set it up), there is part to test the FLEXDMD (through dmddevice.dll)

I see 2 issues :

  • using a real DMD within dmddevice.ini  it doesn't show anything on the screen.
  • using a virtual DMD it works for 1 run, but when testing again, I see the next screenshot in the virtual DMD

image.png.79fc4b5b0764e7180659455a7d87b915.png

 

 

DmdDevice.log log.txt DmdDevice_flexDMD_VirtualDMD.log DmdDevice_FlexDMD_realDMD.log

Edited by MikeDASpike
  • Content Provider
Posted
11 hours ago, Dazz said:

 

@lucky1 So what is your primary hangup?  Why are you holding back everyone from being able to move this hobby forward? 

 

Freezy has my 100% trust in what he has been able to do and in everything he has been doing for this hobby and community.  I think he's done very well to work within your demands for getting this plugin going.  I believe that his intentions are genuine and best for the community. 

 

For the love of the community... Can we please get this over with and move forward?

 

There is a simple reason for this. I currently just don´t have the time to do some testing before releasing the plugin and therefore I waited for freezy to fix stuff which has been introduced due to his updates and changes which are not plugin related. From the post above I see it still has problems which I already reported to freezy from the short tests I was abled to make. As a sidenote we agreed on doing this on march 18th and freezy started to work on this more than 2 months later on may 27th. He released the first beta of this on june 12th and now I´m the one who needs to rush ?  I don´t get why ! I will see if I have the time any time soon to test and release a first version of the plugin for this. 

  • Content Provider
Posted
12 minutes ago, lucky1 said:

From the post above I see it still has problems which I already reported to freezy from the short tests I was abled to make.

 

I just downloaded the 64bit version from the first post and tested ss_15 with pinmame setup.exe . I get exactly the same picture as @MikeDASpike

Posted

@MikeDASpike Thanks! So for you, the rendering issue occurs only through the FlexDMD GUI?

 

@lucky1 There was a lot of work involved porting the plugin system into dmdext. Contrarily to your plugin, which already exists. You even went through the trouble of gutting it, so I couldn't test PAC. You could just release it today with zero effort. You're stalling. I guess it gives you some kind of leverage, over... I don't know.

Posted

@MikeDASpike I still can't reproduce, since "Stop" here doesn't do anything:

 

image.thumb.png.bf08df2f661e98d91a61a94cb509465e.png

 

So I can't really repeat it, apart from quitting the app and re-launching.

 

Could you by any chance share your DmdDevice.ini so we can have identical setups? Also I've noticed that you've placed the DLL into a separate folder DMDextTest, I know this is a long shot, but did you try putting it into your normal directory where you have the working version?

 

EDIT: Also, if you can describe step-by-step how you get the render error, that'd be useful. I found out by switching tabs it will re-init the dmddevice, but even there I'm not getting those errors.

Posted

@freezy
I tested in a different dirrectory as I had some issues.
I just moved it back to my pinmame directory ande-register FLEX DMD

So on real DMD, i don't get anything during test,.
Attached my Dmddevice.ini (it's a pretty old (straight forwarded) one and DMDdevice.log from the original directory.

 

The stop button works with older dmddevice.dll, but when I switch from tab (as you mentioned), i get this behaviour.

See next video I created :

 

 

DmdDevice.ini DmdDevice.log

Posted

Not sure if it helps, but PinballX shows a bit the same behavior as FleDDM gui.
When using a real DMD I don't see anything on the DMD.
When I chnage the output to virtual DMD, I get the blurry colors on my virtual DMD.

 

image.thumb.png.6f3c296d538215f02665f0aaca1d137f.png 

Posted

I've now tried to reproduce on two different PCs with no luck. Is there any notable third party software you've installed that could cause this? Otherwise I'll need to debug this remotely, I'll ping you on Discord later today..

  • Content Provider
Posted

It is only happening with a dmddevice.ini in place and on the first "Start" of a ROM in setup.exe.

The display is then working fine when you "Stop" and "Start" the ROM again.

Maybe this helps narrowing down the issue.

 

  • Content Provider
Posted

I made a short debug and on the first start which is not working in the _style structure these values are present

 

first.png.7f23f3ac1e20d9093b4cfd8328fb6632.png

 

and in the second these

 

Second.png.679abd94b1b4ae6a4c357c99d2d1aafd.png

 

 

Posted
3 hours ago, Meshuggah said:

I and one other person I know of cant get the DMD to stretch vertically only horizontally..  64 bit

I just tried JP's new Totanv5 with vpx 10.8 beta 1307x4 DX and Lucky1's dll's and it is sizeable same as before. Did you check whether you have keep aspect ratio checked when you right click on it? Are you running DX or GL version of vpx? I don't think that matters but might

Posted
19 hours ago, Cliffy said:

I just tried JP's new Totanv5 with vpx 10.8 beta 1307x4 DX and Lucky1's dll's and it is sizeable same as before. Did you check whether you have keep aspect ratio checked when you right click on it? Are you running DX or GL version of vpx? I don't think that matters but might

I'm running the non GL 10.8  I found that if I click Ignore aspect ratio I can do what I want with it.. something I didn't have to do in previous versions.. no problem after that except the previously mentioned Blurry Lighting.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...