4027 replies to this topic

[digitalarts]

Hi,

I think the "old" .pal/.vni  files needs to be named as "pin2dmd.xxx"

The "new" .pac files can be named anyway, ie  "mypin.pac" (as long as only ONE .pac file sits inside the folder)

[fripounet]

same property as other plastics, so why this transparency?

 

[lukpcn]

I have just checked the latest rev. 306 and it is still not working on my win10 pincab, it doesn't open, but if I set it to run in win 8 compatibility mode then it works, same with rev. 277. Maybe that's a hint for You guys.
Tried to play Batman 66 in compatibility win 8 mode and it crashed script on start so it is not a way to use it.

[BrandonLaw]

Chiming in.  306 also a bust considering the builds of late.  Compatibility does fire up the program on Win10 DT mode here, but on JP's Iron Maiden v4 produces errors.  Went back to Thalamus' latest compile with no compatibility mode and it works fine.

[jpsalas]

The strange thing is that I do not have any problem at all with any beta revisions. All of them work very well.

I do not run the exe in any compatibility mode and I do not run it as administrator either.

 

I have an older cpu, and that can be the difference. I have an Intel i7 10700K, and a RTX 380. And until now I was running Windows 10 Pro, but a few weeks ago I installed Windows 11 Pro, and everything seems to work just as fine.

But I know there were some problems with Intels 12th generation CPU's. But I thought they were fixed in OS updates. 

 

I know my comment doesn't help much, but at least you know that the latest beta works on some setups

[fourbanks]

The strange thing is that I do not have any problem at all with any beta revisions. All of them work very well.

I do not run the exe in any compatibility mode and I do not run it as administrator either.

 

I have an older cpu, and that can be the difference. I have an Intel i7 10700K, and a RTX 380. And until now I was running Windows 10 Pro, but a few weeks ago I installed Windows 11 Pro, and everything seems to work just as fine.

But I know there were some problems with Intels 12th generation CPU's. But I thought they were fixed in OS updates. 

 

I know my comment doesn't help much, but at least you know that the latest beta works on some setups

Same here all good 

[BrandonLaw]

The strange thing is that I do not have any problem at all with any beta revisions. All of them work very well.

I do not run the exe in any compatibility mode and I do not run it as administrator either.

 

I have an older cpu, and that can be the difference. I have an Intel i7 10700K, and a RTX 380. And until now I was running Windows 10 Pro, but a few weeks ago I installed Windows 11 Pro, and everything seems to work just as fine.

But I know there were some problems with Intels 12th generation CPU's. But I thought they were fixed in OS updates. 

 

I know my comment doesn't help much, but at least you know that the latest beta works on some setups

 

Agree.  Couple revs back on cab but works fine on win 11/Ryzen/3070

[Cliffy]

Finally got my first glitch today. 10.7.2 rev 315. JP just updated his Serious Sam tables and on Sam 2 the shoot again insert artwork and lamp is clipped off at the bottom. Works fine with rev 289 and Sam 1 doesn't show a problem with either version. 

Edited by Cliffy, 01 October 2022 - 12:45 AM.

[jpsalas]

Finally got my first glitch today. 10.7.2 rev 315. JP just updated his Serious Sam tables and on Sam 2 the shoot again insert artwork and lamp is clipped off at the bottom. Works fine with rev 289 and Sam 1 doesn't show a problem with either version. 

 

 

Yes, I get that too with revision 306. I have been using rev 285 and the glitch is not there.

That "glitch" is the LUTbox on the desktop. It is a simple text box which should be transparent, but something happened between rev 285 and 306. I can download all the revisions in between and I'll find which one started to feil.

 

Finally got my first glitch today. 10.7.2 rev 315. JP just updated his Serious Sam tables and on Sam 2 the shoot again insert artwork and lamp is clipped off at the bottom. Works fine with rev 289 and Sam 1 doesn't show a problem with either version. 

 

 

Yes, I get that too with revision 306. I have been using rev 285 and the glitch is not there.

That "glitch" is the LUTbox on the desktop. It is a simple text box which should be transparent, but something happened between rev 285 and 306. I can download all the revisions in between and I'll find which one started to feil.

 

 

Revision 289 is the last one where the text boxes are still transparent. I guess it is the C++ compiler revision that didn't work, unless something else changed.

Edited by jpsalas, 01 October 2022 - 02:11 AM.

[Cliffy]

Thanks for confirming JP and thanks for the updates on Sam! Love it 

[clsxalghazanth]

Hi ; Where can i get the rev 315 ? it is only up to rev 281 on github/releases page Thanks

[vbousquet]

Revision 289 is the last one where the text boxes are still transparent. I guess it is the C++ compiler revision that didn't work, unless something else changed.

 

 

I think this may be one of the changes I made regarding unifying VPVR and VPX. I will look for a fix to this. Thanks for tracking it down!

[BrandonLaw]

Hi ; Where can i get the rev 315 ? it is only up to rev 281 on github/releases page Thanks

 

325's up

 

https://github.com/v...runs/3161843866

[vbousquet]

 

Revision 289 is the last one where the text boxes are still transparent. I guess it is the C++ compiler revision that didn't work, unless something else changed.

 

 

I think this may be one of the changes I made regarding unifying VPVR and VPX. I will look for a fix to this. Thanks for tracking it down!

 

This is fixed as of version v327

[wiesshund]

Hi ; Where can i get the rev 315 ? it is only up to rev 281 on github/releases page Thanks

 instead of releases, click actions, and see what the latest build is

that will always show what is the latest beta build

[GCS]

I solved the problem with missing graphics by unchecking Texture Compression in the Video options. I am using the version provided by Enthusiast two posts above.

[Cliffy]

 

 

Revision 289 is the last one where the text boxes are still transparent. I guess it is the C++ compiler revision that didn't work, unless something else changed.

 

 

I think this may be one of the changes I made regarding unifying VPVR and VPX. I will look for a fix to this. Thanks for tracking it down!

 

This is fixed as of version v327

 

Confirmed transparency fixed in 330, thanks guys!

[jpsalas]

 

 

 

Revision 289 is the last one where the text boxes are still transparent. I guess it is the C++ compiler revision that didn't work, unless something else changed.

 

 

I think this may be one of the changes I made regarding unifying VPVR and VPX. I will look for a fix to this. Thanks for tracking it down!

 

This is fixed as of version v327

 

Confirmed transparency fixed in 330, thanks guys!

 

Yes, it works fine again on my computer too

[jpsalas]

I have seen some reduction in the quality of the wire ramps rendering. The last good revision was rev 306. Rev 315 just gives me a rendering error. And from the rev 321 the wire ramps looks worst than before, as you can see in the picture.

 rev306-vs-rev321.png   1.11MB   8 downloads

 

I remember some time ago fuzzel or toxie did something to the VPX wire ramps so they looked much better, like increasing the resolution or something, the same for the rubbers, can it be that the merged VR branch overwrote that extra resolution/rendering pass?

 

As a note this is the error I get with rev 315, so maybe the wire ramps are also of bad quality in this revision, but I cannot run it:

 

[wiesshund]

I have seen some reduction in the quality of the wire ramps rendering. The last good revision was rev 306. Rev 315 just gives me a rendering error. And from the rev 321 the wire ramps looks worst than before, as you can see in the picture.

rev306-vs-rev321.png

 

I remember some time ago fuzzel or toxie did something to the VPX wire ramps so they looked much better, like increasing the resolution or something, the same for the rubbers, can it be that the merged VR branch overwrote that extra resolution/rendering pass?

 

As a note this is the error I get with rev 315, so maybe the wire ramps are also of bad quality in this revision, but I cannot run it:

  rev315.png

 

build 330

can not even run avengers, or any other table

i get just a black screen
and if i disable alt depth rendering (cause AMD) i get a crash with this

 

 

Same with 327

had to go all the way back to build 315 before this stopped
and then i could load a table, but it looked Bad, like yea bad, lot of stuff wrong with it visually
Colors and gamma seem weird
Ramps have lots of jaggys like FSAA is broke or some other rendering issue
Plastics on Zelda are fubar

JP's ramps were all kinds of jaggy, as well as other degraded video aspects
(opened Zelda at random and oof, what happened to the plastics?)

 

Went back to toxies build 306
And all was right as rain again.

So something in the VR stuff seems to be blowing it up for us non VR users
no idea what but maybe the crash that JP and i showed may help?

 

wire ramps, and other things almost look like 4X FSAA is broken for them?

And here is Zelda in build 306
NOTE the Plastics on the slingshots!!

 

Ok now build 315

 

parts of table closest seem to go out of focus?

 

Settings being used during all tests (except where i had to disable flullscreen to get crash dialog)