2087 replies to this topic

[randr]

Vp r930 or higher does respect vpx9 windowed full screen and you can run both no problem. Just do not go in video preferences ever again of vp921 or it will loose windowed full screen.


Sent from my iPhone using Tapatalk

[luvthatapex]

Thanks JP I made sure it was windowed before launching it. The other problem that also happens is any table I tried to load with test11 corrupted the registry so I had to delete the table in the registry, load 9.21 and let it take the defaults again. Bummer.

 

I did have the out of memory error in test11, but the error was mine I was running the table at full screen and not windowed (full screen) So luvthatapex, try setting to that windowed (full screen) and I guess it will be fine.

[boiydiego]

Hi,

 

would it be possible to implement that "Windowed Fullscreen" mode into the official VP921 version? This would save lots of problems, I think, switching between the two builds.

 

Regards

Michael

that would indeed be good.

[DJRobX]

The other problem that also happens is any table I tried to load with test11 corrupted the registry so I had to delete the table in the registry, load 9.21 and let it take the defaults again. Bummer.

 

That's exactly what happens to me when I forget to run the DX9 in Windowed mode.   I've been meaning to do a before/after diff to see what exactly is getting corrupted. 

 

It really sounds like the Windowed mode setting didn't stick for some reason.    I'm wondering if there's even a point in supporting the full-screen modes, since the majority of folks use VPinMame in conjunction with VP, and the result is pretty catastrophic if FS is enabled.

[gogo69]

i played Flintstones_VP91x_1.02FS.vpt yesterday and noticed the gates on the ramps turn black when a ball moves the gate

dx9-v11

[ClarkKent]

It's funny when the ball gets under the transparent plexi on the right upper side in Strikes and Spares - and becomes transparent!

[DreamTrap]

dunno if this has anything to do with dx9 but in atlantis the ball got stuck under the left ramp and in batman when you went up the left ramp it goes over to the right and jumps straight down in the bat cave and gets stuck

[Tropi]

I just recognized a vsync issue with Simpson Pinball Party. It doesn't seem to be related to the DX9 port, because I see the same behavior also in older versions, but maybe this is something that needs correction.

I tested some vsync settings between 120 and 240. The result was always heavy stutter and the FPS jumped every second between 60 and the adjusted rate in the preferences. This makes the table unplayable. This is currently the only table I recognized this behavior. Normally all tables play smoothly with these vsync settings on my cab.

Setting vsync to 0 results in smooth gameplay at 1800 FPS for 921 and ~300 for V11.

 

I also recognized some graphics issues with this table. It is already mentioned in the compatibility table, but I'm not sure if the solution given there addresses my findings.

In the attachment you can see several black objects, that normally are colored. The workaround seems to be to set the transparency to black. As far as I could see (I'm not a table designer) the transparency is already set to black.

 

Win 8.1, Phenom II X4 945, 16 GB RAM, GTX 560

Attached Files

•  921.jpg   213.59KB   11 downloads
•  V11.jpg   209.08KB   11 downloads

[fuzzel]

Just a small side note: the DX9 port is now a part of the official VP subversion repository (rev941)

[maceman]

Is there a 'dynamic' way to add a link to the newest build to each Dev's signature? Would be much easier to download and try these WIP's rather than trying to find the dropbox each time there is an update. I am ready to try JP's newest AFM's update and am still back on 921 rev 845

So much amazing work this past year to 2 years.....Awesome!

Cheers,

MAceman

[freezy]

Just a small side note: the DX9 port is now a part of the official VP subversion repository (rev941)

 

Fantastic. Are you guys gonna switch over to Git completely at some point?

[fuzzel]

Nope

 

 

Just a small side note: the DX9 port is now a part of the official VP subversion repository (rev941)

 

Fantastic. Are you guys gonna switch over to Git completely at some point?

 

Nope

 

 

Is there a 'dynamic' way to add a link to the newest build to each Dev's signature? Would be much easier to download and try these WIP's rather than trying to find the dropbox each time there is an update. I am ready to try JP's newest AFM's update and am still back on 921 rev 845

So much amazing work this past year to 2 years.....Awesome!

Cheers,

MAceman

We devs normaly don't create public binaries. Our "build server" is called Koadic If you would like to try JP's newest AFM you should update to the official 9.2.1 because rev 845 is rather "old"

[mukuste]

 

Just a small side note: the DX9 port is now a part of the official VP subversion repository (rev941)

 

Fantastic. Are you guys gonna switch over to Git completely at some point?

 

 

I would love to but the other devs are having some reservations... so for now it's back to SVN

 

 

@maceman: Best I can offer you is the first post in this thread, which always has links to all versions.

[maceman]

 

 

Just a small side note: the DX9 port is now a part of the official VP subversion repository (rev941)

 

Fantastic. Are you guys gonna switch over to Git completely at some point?

 

 

I would love to but the other devs are having some reservations... so for now it's back to SVN

 

 

@maceman: Best I can offer you is the first post in this thread, which always has links to all versions.

 

 

Thanx Muskuste,

Really the request wasn't just for myself. Others have mentioned getting lost, and I am the one who normally replies with a 'go to Koadic's sig' reply....

The issue is I think everyone here knows the Dev process and how Koadic compiles the builds. My point was that it is often difficult to keep up with the new builds. We have to manually search for koadic's last post or profile to get his sig to download. Newer members will never know to do this.

My idea was to have a dynamic link that when koadic updates, anyone involved with the build(s) would also have the same updated link so one could download the newest build in more than one place. It was just an idea.

The first link in this post will work as well i suppose.

Cheers,

Maceman

[mukuste]

Okay, I see what you mean. But the versions posted in this thread were all test builds, so there was no need for new users to be able to find them, they were mostly used for gathering feedback and finding bugs in the DX9 branch. I never even intended for them to end up in the Dropbox, but I guess there was a demand for it.

 

Going forward I guess there should be a more defined procedure for getting new versions out. Were people generally happy with the one-build-per-SVN-revision model that the VP 9.2 beta threads were using? It seems a bit too fine-grained to me. On the other hand, most hardcore users don't want to wait several months for the next full version. I think something similar to what I did now, about one build per week, could work well, but it really depends on what the community wants.

[DreamTrap]

Just a small side note: the DX9 port is now a part of the official VP subversion repository (rev941)

it olny goes up to 932 in dropbox?

Edited by DreamTrap, 17 March 2014 - 01:53 PM.

[luvthatapex]

Test versions once a week on your WIP is perfect IMHO. It gives us a week to give feedback and everything is contained in one thread.

I think you are doing a fabulous job and shouldn't have to worry about posting things elsewhere. THis is a WIP thread and you are giving us WIP, nothing to change!

 

LTA

 

Okay, I see what you mean. But the versions posted in this thread were all test builds, so there was no need for new users to be able to find them, they were mostly used for gathering feedback and finding bugs in the DX9 branch. I never even intended for them to end up in the Dropbox, but I guess there was a demand for it.

 

Going forward I guess there should be a more defined procedure for getting new versions out. Were people generally happy with the one-build-per-SVN-revision model that the VP 9.2 beta threads were using? It seems a bit too fine-grained to me. On the other hand, most hardcore users don't want to wait several months for the next full version. I think something similar to what I did now, about one build per week, could work well, but it really depends on what the community wants.

[fuzzel]

 

Just a small side note: the DX9 port is now a part of the official VP subversion repository (rev941)

it olny goes up to 932 in dropbox?

 

That's normal. Koadic hasn't compiled it yet.

 

I think we should stop building binaries for every revision. We are now on the DX9 road and that means we should collect multiple revisions/bug fixes into one binary. Perhaps the same thing Murkuste did in the past with his friday releases.

[DJRobX]

I think something similar to what I did now, about one build per week, could work well, but it really depends on what the community wants.

 

I don't think the daily builds hurt anything as long as the devs communicate what revisions they think are ready for testing.   I like the way you tagged the different test builds.   What Mukuste's doing works very well. 

Edited by DJRobX, 17 March 2014 - 03:09 PM.

[maceman]

Okay, I see what you mean. But the versions posted in this thread were all test builds, so there was no need for new users to be able to find them, they were mostly used for gathering feedback and finding bugs in the DX9 branch. I never even intended for them to end up in the Dropbox, but I guess there was a demand for it.

 

Going forward I guess there should be a more defined procedure for getting new versions out. Were people generally happy with the one-build-per-SVN-revision model that the VP 9.2 beta threads were using? It seems a bit too fine-grained to me. On the other hand, most hardcore users don't want to wait several months for the next full version. I think something similar to what I did now, about one build per week, could work well, but it really depends on what the community wants.

 

Thanx M,

I am glad you understand my post

My post was not in regards to your specific work. What you are doing is GREAT and this WIP thread is fine.

It is just very time consuming for myself (and others) who like to test the new WIP builds as they come out. I know enough that if something isn't working to revert back a Wip or go back to the latest official release, but it would be nice to be able to

quickly find.As you can see, I was 2 months behind in my revision, and that is simply because of not being aware of the updates. Too many posts to follow in too many forums i suppose.

cheers,

Maceman