143 replies to this topic

[reko19]

works like a charm, thank you. looks like it is not consistent for all stern games, no #46 for monopoly?

Edited by reko19, 20 April 2020 - 01:56 AM.

[jpsalas]

In all these versions 3.0 of my tables I have used a more colorful HDR image to give a more warm look to the metals. The image is in low quality just to give a more subtle reflections on the metals. And I made that image by combining different images.

[Thalamus]

Thank you very much Juan for all of the updates today. LOTR is especially appreciated, as it is one of my favorite Sterns. I look forward to play them all with the new physics.  

[jpsalas]

UPDATE

 

3.0.1 Updated 12.01.2022

- Added blinking state to the arrows

- Fixed ring diodes

- Adjusted backwall diodes

- Adjusted flashers

- Adjusted physics to latest Arcade 3,01

 

This update was done mostly to add a blinking to the arrows when you read on the DMD "Shoot the blinking lights". I guess those arrows are modulated somehow, but they are not 100% emulated in the current vpinmame, So I simply "faked" them   Then at the same time I could update a few other things

At last the ring diodes work as they should be working

[bolt]

Thank you for the update JP.

[RYSr]

Thanks for the update!

I'm having a problem table is crashing VP 2 seconds after loading just before the ROM activates.

I'm running 10.7 final, your table version 3.0 runs fine.

[teisen]

Just yesterday I was reviewing my LOTR tables... I have several, one more beautiful and well made than the other... but for me, the best playing is without a doubt the one made by JP... incredible!!!

 

I don't know what magic, sorcery or voodoo this is, but JP's tables are fantastic!!!

 

thanks for the update

 

hugs

[jpsalas]

Thanks for the update!

I'm having a problem table is crashing VP 2 seconds after loading just before the ROM activates.

I'm running 10.7 final, your table version 3.0 runs fine.

 

I saved the table with 10.7 final, so that can't be a problem. Have you copied over all the dll and vbs from 10.7? And not only the exe file? (I had to ask )

Anyway the table hasn't anything special, sounds or images, so I don't know what could crash VPX. Do you get a crash.txt?

[toxie]

It could be the AT91 JIT problem/crash in PinMAME.   :/

[Mrtr32]

Thanks JP for this awesome table

 

The playability and visual are excellent!

[wiesshund]

Thanks for the update!

I'm having a problem table is crashing VP 2 seconds after loading just before the ROM activates.

I'm running 10.7 final, your table version 3.0 runs fine.

 

Sounds more like your vpinmame is crashing, which will take VPX out with it in the process

You might check the ROM?

Make sure ddraw is disabled

etc

Edited by wiesshund, 12 January 2022 - 07:27 PM.

[RYSr]

It could be the AT91 JIT problem/crash in PinMAME.   :/

I did a windows update yesterday before I tried the v3.01 table. But I did a shutdown and reboot after the crash, and it still crashed again.

I Just tried it today and it's working OK.. I did check the AT91 Jit and it's set to 1. As I mentioned  JP's lotr v 3.0 worked ok last night even though the v3.01 crashed. Strange?

Thanks everyone for the replies.

Here's the crash Txt:

Crash report VPX rev367 (e242d7c)
============
Process: VPinballX 10.7-Final.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:1FA50002
Attempt to read from 0x1FA50002
Thread ID: 0x25E0 [9696]

Call stack
==========
1FA50002  (0x178C9AA8 0x0000038B 0x00000000 0x1fa50002)
26A0C810 VPinMAME.dll (0x00000000 0x00000000 0x26BD5F05 0x0000038b)
26BD5F05 VPinMAME.dll (0x0000038B 0x00000020 0x17861DC0 0x1ba8fec8)

Environment
===========
Date/time: 12/1/2022, 09:15:18:82
Number of CPUs: 4
Processor type: 586
System: Unknown Windows version - 6.3 (9600)

Memory status
=============
Total Reserved: 136872K (133M) bytes
Total Commited: 736748K (719M) bytes
Total Free: 3320620K (3242M) bytes
Largest Free: 2095336K (2046M) bytes

Registers
=========
EAX=1FA50002 EBX=1BA8FE94 ECX=1FA50002 EDX=00000000
ESI=0000038B EDI=0000038B EBP=00000000 ESP=1BA8FE9C EIP=26BD5F05
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

 

Edited by RYSr, 13 January 2022 - 12:02 AM.

[ludovids]

One of my favorite tables just got better. Thanks JP!

[naeromagus]

Thanks for the Update Especially the Fixes to use the Blinking Lights During the Modes. I had always wondered why this table did not blink during the modes They would just stay solid. Figured something to do with the emulation. Either way leave it to JP to Find a solution> Thanks !

[jpsalas]

Toxie has fixed vpinmame so LOTR and other Whitestar tables (Nascar, Apollo 13, ++) have now arrows that flicker So other LOTR tables will have also blinking lights

 

The new vpinmame can be download from here: https://www.vpforums...=76#entry494106

Edited by jpsalas, 13 January 2022 - 08:02 AM.

[toxie]

 

It could be the AT91 JIT problem/crash in PinMAME.   :/

I did a windows update yesterday before I tried the v3.01 table. But I did a shutdown and reboot after the crash, and it still crashed again.

I Just tried it today and it's working OK.. I did check the AT91 Jit and it's set to 1. As I mentioned  JP's lotr v 3.0 worked ok last night even though the v3.01 crashed. Strange?

Thanks everyone for the replies.

Here's the crash Txt:

Crash report VPX rev367 (e242d7c)
============
Process: VPinballX 10.7-Final.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:1FA50002
Attempt to read from 0x1FA50002
Thread ID: 0x25E0 [9696]

Call stack
==========
1FA50002  (0x178C9AA8 0x0000038B 0x00000000 0x1fa50002)
26A0C810 VPinMAME.dll (0x00000000 0x00000000 0x26BD5F05 0x0000038b)
26BD5F05 VPinMAME.dll (0x0000038B 0x00000020 0x17861DC0 0x1ba8fec8)

Environment
===========
Date/time: 12/1/2022, 09:15:18:82
Number of CPUs: 4
Processor type: 586
System: Unknown Windows version - 6.3 (9600)

Memory status
=============
Total Reserved: 136872K (133M) bytes
Total Commited: 736748K (719M) bytes
Total Free: 3320620K (3242M) bytes
Largest Free: 2095336K (2046M) bytes

Registers
=========
EAX=1FA50002 EBX=1BA8FE94 ECX=1FA50002 EDX=00000000
ESI=0000038B EDI=0000038B EBP=00000000 ESP=1BA8FE9C EIP=26BD5F05
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

 

 

Can you please try again, but setting the AT91 jit thing to 0?

Toxie has fixed vpinmame so LOTR and other Whitestar tables (Nascar, Apollo 13, ++) have now arrows that flicker So other LOTR tables will have also blinking lights

 

The new vpinmame can be download from here: https://www.vpforums...=76#entry494106

Please all try the various whitestar tables then! And report in that thread if something is now fishy..

[wiesshund]

I have LOTR and Apollo 13
Not 100% sure what i am to be looking for?
They work fine in Vpinmame 3.5

 

if someone can show me exactly what i am supposed to test?

I ran Apollo 13 and stuff was blinking, but i dont know if it was or was not blinking before or if i am looking at the right things?

[jpsalas]

I have LOTR and Apollo 13
Not 100% sure what i am to be looking for?
They work fine in Vpinmame 3.5

 

if someone can show me exactly what i am supposed to test?

I ran Apollo 13 and stuff was blinking, but i dont know if it was or was not blinking before or if i am looking at the right things?

 

Just check that the lights work just like in vpinmame 3.4, only that now some lights may blink fast when before they were simply on. If all the lights seems to be working then I guess everything is ok Report in the vpinmame thread if some light don't seems to work.

[haggi]

Thank you for this wonderful implementation and update.

Looks beautiful as always and is very playable.

 

A special thanks also for the setting options.

Your tables can be easily adjusted to my own preferences

Light workload with maximum fun

 

I hope it stays that way.

[MrGrynch]

Hi!  Great Table JP!  Thank you!

 

I might be really daft, but I don't have a backglass for this.  Does one exist?  Do I use a different one?

 

sorry for the noob question!

 

BTW... I also started on Pet/C64 back in the day.  Specialty was breaking copy protections and drive programming.  Broke V-Max (not the first to do it).  Did the demo scene for a long time under tha handle Sir Sid