1972 replies to this topic

[unclewilly]

Is anyone who is working in the editor a lot experiencing problems with the properties panel and getting a double visuals tab for an object. Easiest way I've found to reproduce is to enable the view playfield image. Add a primitive to the table and set the image. It doesn't happen all the time but often enough that when I set the image the tableimage in the editor will disappear although still shows as being visible in the menu thenthe properties panel will show 2 visual tabs for the primitive, 1 for the prim and one for the table.
Setting don't get saved after this occurs or are sometimes applied to the table rather then the primitive.
Other issue is adding a new layer. Selecting an object from another layer and trying to assign it to the new layer but the new layer does not appear in the assign menu.

Just wondering if it's just me

[wiesshund]

Are You planning to implement DX12 or Vulkan in future versions of VPX? What changes/new features can we expect in VPX11?

 

Me?

I would not know where to begin.

 

I do know, from reading the whitepaper, that it would be a massive undertaking, and would probably consume the entire beta dev cycle with no other changes taking place.

[ryesteve]

Need some help with ini files.  How do I keep the pov parameters in the .ini from getting wiped out when I save a table?  What typically happens is, I F6 the table, set the POV, generate the .ini, and then when I start playing it, maybe I decided to swap out the ball image.  I do that, save the table, and then when I reload the table, I find the pov is back to the default, because the parameters I originally generated in the ini are no longer there.

Edited by ryesteve, 09 January 2024 - 03:17 AM.

[robertms]

 

Need some help with ini files.  How do I keep the pov parameters in the .ini from getting wiped out when I save a table?  What typically happens is, I F6 the table, set the POV, generate the .ini, and then when I start playing it, maybe I decided to swap out the ball image.  I do that, save the table, and then when I reload the table, I find the pov is back to the default, because the parameters I originally generated in the ini are no longer there.

 

 

Saving the table should not affect the ini file. Make sure you're not renaming the table as that would put your saved ini file out of sync. Double check the vpx and corresponding ini files in your tables folder to ensure they're named identically.

[ryesteve]

 

 

Need some help with ini files.  How do I keep the pov parameters in the .ini from getting wiped out when I save a table?  What typically happens is, I F6 the table, set the POV, generate the .ini, and then when I start playing it, maybe I decided to swap out the ball image.  I do that, save the table, and then when I reload the table, I find the pov is back to the default, because the parameters I originally generated in the ini are no longer there.

 

 

Saving the table should not affect the ini file. Make sure you're not renaming the table as that would put your saved ini file out of sync. Double check the vpx and corresponding ini files in your tables folder to ensure they're named identically.

 

 

No, it's not a file-naming issue.  I'm actually opening the .ini in an editor and I can see the block of parameters I just generated relating to the pov is no longer there.  If I go back into the F6 and set it up again and regenerate the ini, it's back and the table looks fine.

[robertms]

 

 

 

Need some help with ini files.  How do I keep the pov parameters in the .ini from getting wiped out when I save a table?  What typically happens is, I F6 the table, set the POV, generate the .ini, and then when I start playing it, maybe I decided to swap out the ball image.  I do that, save the table, and then when I reload the table, I find the pov is back to the default, because the parameters I originally generated in the ini are no longer there.

 

 

Saving the table should not affect the ini file. Make sure you're not renaming the table as that would put your saved ini file out of sync. Double check the vpx and corresponding ini files in your tables folder to ensure they're named identically.

 

 

No, it's not a file-naming issue.  I'm actually opening the .ini in an editor and I can see the block of parameters I just generated relating to the pov is no longer there.  If I go back into the F6 and set it up again and regenerate the ini, it's back and the table looks fine.

 

 

Which version of the 10.8 beta are you using? The most current version is 1852. Have you tried launching the table followed by F12 to enter the adjustment mode, then hit start (or 1) to save, followed by F12 to exit adjustment mode? I just tried this using the new Rocky & Bullwinkle table and had no issues. After making the POV adjustments in F12 I exited back to the editor, imported and swapped out the ball image, saved the table via the 'file' menu and shut down the editor. When I restart the editor and launch the table again all my new settings remain active (including the new ball).

[Mike DA Spike]

Vulcan is more modern, more GPU efficient, and is what professional graphics software and hardware developer are moving to... and its cross platform.

OpenGL has been "legacy" for many years and game design studios use DirectX and starting to use Vulkan... no one uses OpenGL.  If VPX wants to attract new coders 

 

 

100% true. But be aware that VP is from 2009 and was build for DX9.
starting from 10.8, VP has a GL version (mostly for VR and 3d anaglyphic) and because GL is also CPU independent, it can now be compiled to other OS/CPU's

 

I suggest they code using tools professionals use. Otherwise, when 'old skool' coders leave, VPX development dies

 

VP is a free tool and developers spends a lot of time on it to make new features and releases . If you want to suggest that the dev's should use professional tools and move to next level graphics, please volunteer and join the DEV's and make it happen !
It's always easy to speak for others, but if you want stuff, just do it !

Vincent spend almost a year to make the GL version workable, with a Live editor, new POV etc.

About new tools, Freezy and team started to use unity and make all VP backwards compatible. This project is running for years already and all in spare time and free of costs.

 

Are You planning to implement DX12 or Vulkan in future versions of VPX? What changes/new features can we expect in VPX11?

 

Me?

I would not know where to begin.

 

 

Start with the following in your C# program:

using Silk.NET.Vulkan;

Even I understands (and that means a lot) : drinks: 

Edited by Mike DA Spike, 09 January 2024 - 05:19 AM.

[wiesshund]

 

 

 

Start with the following in your C# program:

using Silk.NET.Vulkan;

 

That's like starting a faerie tale with
Once Upon a Time...

 

Dont get much farther than that, unless you have it planned out ahead of time

 

Though i would probably have to do DX12 1st, as Nvidia users would fair better with it than Vulkan

and then, i may as well multithread it while i am at it and have to all torn apart on the floor,

[jpsalas]

Is anyone who is working in the editor a lot experiencing problems with the properties panel and getting a double visuals tab for an object. Easiest way I've found to reproduce is to enable the view playfield image. Add a primitive to the table and set the image. It doesn't happen all the time but often enough that when I set the image the tableimage in the editor will disappear although still shows as being visible in the menu thenthe properties panel will show 2 visual tabs for the primitive, 1 for the prim and one for the table.
Setting don't get saved after this occurs or are sometimes applied to the table rather then the primitive.
Other issue is adding a new layer. Selecting an object from another layer and trying to assign it to the new layer but the new layer does not appear in the assign menu.

Just wondering if it's just me

 

No. It's not only you, I'm experiencing the same thing, although I didn't know how to reproduce it I have had up to 3 Visual tabs!

And the layers work when they feel to do it, but many times when I add a new layer and try to rename it, it simply hangs, and I can't click on it anymore. But I can save the table, open it and I can create the layer again. Also when renaming a layer, with objects in it, it may also hang, but the layer does not disappear when I open the table again.

[wiesshund]

 

Is anyone who is working in the editor a lot experiencing problems with the properties panel and getting a double visuals tab for an object. Easiest way I've found to reproduce is to enable the view playfield image. Add a primitive to the table and set the image. It doesn't happen all the time but often enough that when I set the image the tableimage in the editor will disappear although still shows as being visible in the menu thenthe properties panel will show 2 visual tabs for the primitive, 1 for the prim and one for the table.
Setting don't get saved after this occurs or are sometimes applied to the table rather then the primitive.
Other issue is adding a new layer. Selecting an object from another layer and trying to assign it to the new layer but the new layer does not appear in the assign menu.

Just wondering if it's just me

 

No. It's not only you, I'm experiencing the same thing, although I didn't know how to reproduce it I have had up to 3 Visual tabs!

And the layers work when they feel to do it, but many times when I add a new layer and try to rename it, it simply hangs, and I can't click on it anymore. But I can save the table, open it and I can create the layer again. Also when renaming a layer, with objects in it, it may also hang, but the layer does not disappear when I open the table again.

 

Yea even 10.7.2 does that.

The layers panel craps out and it looks like there are no layers.

Sometimes only part of the layers vanish visually

Layers panel becomes non useable though at that point.

 

 

They are there and fine and all, but you have to save exit and re-open if you need to access them again

[bigus1]

For what it's worth, 9 times out of 10 when the main page wigs out, I find I can toggle to backglass view and back and it's happy again, allowing me to recover my work.

[Pete248]

Is there anyone here that prefers the 3d appearance over and above a standard 4k appearance? Even though I have never see the 3d in action, it seems like it might be more along of the lines of a gimmick. Could be wrong.

 

 

If you've had asked me this question 6 month ago, I would have agreed. Yes it is it a gimmick.

 

But with the new windowed POV AND frame pacing synchronization mode things have changed completely, at least for me:

 

With the new windowed POV I now can get a realistic 3D view. It is as good as the immersive experience I’ve got with VPVR but without the hassle of wearing a VR headset. In some aspects it is even better: I do not have limited FOV and the resolution of objects at the back of the playfield is significantly better than with my HP Reverb G2 (which was said to be the gold standard for VPVR back then). In addition I'm not isolated from the environment, can switch with a single key to 2D (in case other's without glasses want to watch the playfield) and the passive 3D glasses are much more comfortable to wear. I need prescription glasses to play so got a set of clip-on 3D glasses. You probably would not realize that I wear 3D glasses if you see me playing.

 

With frame pacing old 60 Hz TVs have the same low input lag as the newest 144 Hz gaming monitors. This is important because 3D TVs have been discontinued in 2016 and at that time 60 Hz was the maximum frame rate available.

 

I wonder whether the devs who implemented frame pacing in 10.8 had especially these 60 Hz 3D TVs in mind. 120 Hz is almost the standard now for newer TVs and the benefit you get from switching to frame pacing is only 50% of what you see on a 60 Hz TV. With the just announced 480 Hz LG OLED frame pacing likely won't give you any advantage at all. So with newest TVs frame pacing is already obsolete. That said, devs please keep working on the feature for the sake of 3D TV users.

 

For me the combination of windowed POV, frame pacing and a passive 3D TV is such a game changer that I've decided to rework the placement of the playfield monitor in the new cab I'm currently building. I've originally started with the recommended layout according to the Pinscape build guide. Lowering the TV in the back to give the impression of depth with LED matrix at the back and LED strips on the side. In 3D windowed POV this looks strange, like looking into a cab that sits inside a cab.

 

IMO nowadays you have to decide whether you build a cab primarily for 2D with occasional 3D usage or primarily for 3D with occasional 2D usage. Cabinet build guides need to be updated.

 

I've now opted to build for 3D and thus decided to mount the TV almost flush with the glass, with just enough space to mount the LED strips inside a 60° channel on top of the TV bezel. The matrix will be mounted at around 30-45° to fill the gap between TV and backbox. If it looks goofy at that angle I can switch it off so it serves just as a cover.

 

If I could start from scratch, I’d probably build a slightly shorter cab that perfectly fits my 43“ TV left/right/bottom/top and mount the TV flush below the glass. But that won't happen.

 

Well, maybe we’ll see a 3D OLED or Micro LED TV with 21:10 aspect ratio using passive glasses or even no glasses at all somewhere in the future that fits perfectly in a Williams Widebody Cabinet. I'd buy it in a heartbeat.

 

If only this 'horizontal scale by 2' issue (#1230) in 3D interlaced would be fixed. Toxie, Vincent or whoever is able to fix this, please do it. Or as a temporary workaround make it possible to switch from anaglyph to 3D interlaced with F10. You would make me very happy.

  

[Drybonz]

Looks like vbousquet is back in action and there is a new github action #2578 "Update core.vbs for latest PWM outputs in PinMame".  I often don't know what an action is, exactly, based on the title, but this might address the complaints about distorted sound in pinmame.

[ryesteve]

 

 

 

 

Need some help with ini files.  How do I keep the pov parameters in the .ini from getting wiped out when I save a table?  What typically happens is, I F6 the table, set the POV, generate the .ini, and then when I start playing it, maybe I decided to swap out the ball image.  I do that, save the table, and then when I reload the table, I find the pov is back to the default, because the parameters I originally generated in the ini are no longer there.

 

 

Saving the table should not affect the ini file. Make sure you're not renaming the table as that would put your saved ini file out of sync. Double check the vpx and corresponding ini files in your tables folder to ensure they're named identically.

 

 

No, it's not a file-naming issue.  I'm actually opening the .ini in an editor and I can see the block of parameters I just generated relating to the pov is no longer there.  If I go back into the F6 and set it up again and regenerate the ini, it's back and the table looks fine.

 

 

Which version of the 10.8 beta are you using? The most current version is 1852. Have you tried launching the table followed by F12 to enter the adjustment mode, then hit start (or 1) to save, followed by F12 to exit adjustment mode? I just tried this using the new Rocky & Bullwinkle table and had no issues. After making the POV adjustments in F12 I exited back to the editor, imported and swapped out the ball image, saved the table via the 'file' menu and shut down the editor. When I restart the editor and launch the table again all my new settings remain active (including the new ball).

 

 

Using 1807 (beta 7).  I haven't tried using F12 to get into the options menu, just F6.  But everything you described above is what I'm doing, except for how I'm getting in and out of the options menu.  I'll play around with it some more today and see what happens.

[Itchigo]

Can someone shed some light on this (Toxie or whoever)? I've been fighting the cursor missing during play for quite a while. Is there something I need to update or something?? I tried several vp versions after it was supposedly fixed. I just tried this version which is well past when the ticket was closed months ago. VPinballX-10.8.1-1918-bb7524c-Release-win-x64. This problem started with 10.80. in 10.72 it works fine, I have a cursor.

 

This means anytime I have to change a rom setting via F6, I can't see what I'm checking. I have to use 10.72 to change my options, then play in 10.8.

 

This is in windows 7x64. I have enable mouse during play checked.

Edited by Itchigo, 10 January 2024 - 12:16 AM.

[jpsalas]

Can someone shed some light on this (Toxie or whoever)? I've been fighting the cursor missing during play for quite a while. Is there something I need to update or something?? I tried several vp versions after it was supposedly fixed. I just tried this version which is well past when the ticket was closed months ago. VPinballX-10.8.1-1918-bb7524c-Release-win-x64. This problem started with 10.80. in 10.72 it works fine, I have a cursor.

 

This means anytime I have to change a rom setting via F6, I can't see what I'm checking. I have to use 10.72 to change my options, then play in 10.8.

 

This is in windows 7x64. I have enable mouse during play checked.

 

I only get the cursor when I hit "D" to open the debug window. Then I can can see the mouse arrow, and also after I close the debug window.

[tinyhorsesinmytea]

Newest beta breaks VR for me. Launches in my headset in some weird skewed image you see in the lower left corner of your eye. Any ideas? 

[robertms]

Newest beta breaks VR for me. Launches in my headset in some weird skewed image you see in the lower left corner of your eye. Any ideas? 

 

Which newest beta? What is the version number? There are a couple different forks, do not use anything labeled 10.8.1 as it is not ready for general public, use only 10.8.0 files labeled "master".

[tinyhorsesinmytea]

 

Newest beta breaks VR for me. Launches in my headset in some weird skewed image you see in the lower left corner of your eye. Any ideas? 

 

Which newest beta? What is the version number? There are a couple different forks, do not use anything labeled 10.8.1 as it is not ready for general public, use only 10.8.0 files labeled "master".

Yes, the 10.8.0 beta 8

Figured it out. I had to disable the supersampling and then everything rendered normally in the headset. Unfortunately, this version is performing significantly worse so I reverted back to what I was using before until I upgrade my GPU. It’s struggling to run the newest VPW releases in VR anyways but I might just go ahead and get a 4700 ti Super if I can get my hands on one at the end of the month. 


​Now what the hell is going on with the formatting on this forum? Oh whatever. Haha

Edited by tinyhorsesinmytea, 10 January 2024 - 04:35 AM.

[wiesshund]

 

​Now what the hell is going on with the formatting on this forum? Oh whatever. Haha

 

 

uh yea, it kinda be like that.

No idea why it does it.