740 replies to this topic

[DuMichAuch]

For Taito Tables you have to went back to the old taito.vbs, too...

Edited by DuMichAuch, 03 October 2017 - 05:17 PM.

[toxie]

yeah, sorry, a last minute change (of course untested) was responsible for this, fix is in..  :/

[fuzzel]

rev3235 is up

 

- vbs scripts should work again now

- Sound Manager: remove *BG* from the file name, instead toggle Table/Backglass in the output column

[GInsonic]

Great, thanks for all guys!

[DJRobX]

Weird problem: On my laptop (mac with ATI video/parallels), VPX will not display lights on the backdrop.    I've never really noticed this until now because I'm trying to display the score on a segment display for Fire!.   The new Class of 1812 VPX also has the issue.    

 

Internal DMD rendering on the backdrop on DMD tables works perfectly fine, and the table lights all work fine.  I've tried various options (alternative depth buffer, true fullscreen, windowed, etc) and none seem to make a difference. 

 

It does work correctly on my cab, so it's probably something video driver specific, but it's just odd because I've never seen an issue with table lights.   

Edited by DJRobX, 06 October 2017 - 09:09 PM.

[toxie]

most of the backdrop code uses some 'semi-official' way of rendering things via DX9 (e.g. most drivers (=most AMD and NVIDIA ones) get this done, but Intel ones for example fail).

the backdrop rendering code itself needs to be badly rewritten in that aspect but this was always delayed for when multi-monitor support, etc would happen as then it would have to be changed anyway.. :/

[DJRobX]

The decals and backdrop itself render fine, just not the lights.  It's like they don't exist.   So weird...

[DJRobX]

*Edit* forum posted response to wrong board

Edited by DJRobX, 07 October 2017 - 04:54 AM.

[jpsalas]

 

rev3235 is up

 

- vbs scripts should work again now

- Sound Manager: remove *BG* from the file name, instead toggle Table/Backglass in the output column

 

 

I just wanted to say that this build is quite stable. I had a few crashes, but I guess it was because I opened/run a VP9 table several times while I was editing. I have not had a single crash while selecting with the mouse, thanks!

[fuzzel]

 

 

rev3235 is up

 

- vbs scripts should work again now

- Sound Manager: remove *BG* from the file name, instead toggle Table/Backglass in the output column

 

 

I just wanted to say that this build is quite stable. I had a few crashes, but I guess it was because I opened/run a VP9 table several times while I was editing. I have not had a single crash while selecting with the mouse, thanks!

 

Thanks for the feedback. Let's hope we resolved most of these bugs

[BorgDog]

It came up in a conversation regarding the enable mechanical plunger button on a plunger object.  I believe it's been brought up before, but is there any reason why this button would not be checked?  I don't think it has any impact if you don't have a mechanical plunger, and if you have one you definitely want it checked.  If you add a new plunger object now it is not checked, can we at a minimum have that checked by default, and if there really is no reason to not have it checked lets just remove that button and have mechanical plunger always enabled in the code.

 

Thanks.

[toxie]

I do not know enough about the implications, and i also do not remember the exact outcome of the previous discussions.. :/

Anybody knows what the state was back then?

The decals and backdrop itself render fine, just not the lights.  It's like they don't exist.   So weird...

 

Backdrop is 'safe' code, the decals i do not remember, but the backdrop lights definetly used the 'not-so-standard-conform' DX9 code..

[flupper1]

I have been at it all day, and no crashes anymore for me! 

[DJRobX]

I believe it's been brought up before, but is there any reason why this button would not be checked?

 

 

You may have other plunger objects on the table that you do not want the mechanical plunger to affect...

[sliderpoint]

They could be disabled for those. I think he just means, by default it should be on. How often are they used in other areas?  They could be used a lot more if they could have the direction changed.

 

I would also like to suggest that 'primitives' NOT be collidable by default.

 

-Mike

[nFozzy]

Might be a bug too, 'set as default' doesn't work with primitive objects

[ClarkKent]

I get crashes with the latest release when opening the sound manager and reimporting a new sample. Sometimes it works, sometimes it crashes when importing a second one...

[fuzzel]

Might be a bug too, 'set as default' doesn't work with primitive objects

What exactly doesn't work?

[nFozzy]

Set as Default makes any object settings the new default for that object type. Doesn't work with primitives objects, so they always start with 100/100/100 scale with collidable physics on.

[fuzzel]

You're right. Is fixed in the next update.