So not much new from VPVR side, but at least I closed the gap to the VPX development. It worked for me, but when you find any bugs, crashes or other stuff, I'll try to fix it as soon as possible.
https://sourceforge....cts/vpvr/files/
Posted 24 February 2020 - 08:54 PM
So not much new from VPVR side, but at least I closed the gap to the VPX development. It worked for me, but when you find any bugs, crashes or other stuff, I'll try to fix it as soon as possible.
https://sourceforge....cts/vpvr/files/
Posted 24 February 2020 - 11:22 PM
Thanks Caligula,
I let my son borrow my VR setup and he hasn't returned it yet he and the grandkids are loving it.
Guess I'll have to buy newer rig to alternate for VPVR on my PC and Cab, I miss it.
I loaded a table with it in regular VPX mode and I love the new 10.7 beta version editor graphics update and the Tabs on the properties section. I don't think a new VPX 10.7 beta thread and releases are even out yet. The devs have been busy
Edited by RYSr, 24 February 2020 - 11:24 PM.
Posted 26 February 2020 - 07:17 AM
Hi Caligula,
Thanks so much for your work on VPVR, I've been wondering what VR's killer app will be since I got a DK1, and I believe VPX / VPVR is it, for me at least.
I've almost, almost got it working, but I'm suffering from horrible judder / stuttering caused by some kind of problem with headset tracking. Details in this thread, I'm posting here too because I installed the VPVR0.7 update first, before trying out the main releases, so I'm wondering a few things:
a) is the VPVR 0.7 update compatible with VPX 10.6?
b) would you expect any issues to arise from simply replacing the VPVR0.7.zip files with the older VPVR.zip files?
c) Is it worth trying to completely remove VPX and starting from scratch?
d) when is it appropriate to use the 64bit version? Should I match my OS or is there a 64bit version of VPX I should be using?
Thanks for any light you may be able to shed on this issue. I haven't ruled out that it's a Radeon specific issue, I'm using an RX 480 and had to select "RGBA 16F" to get the table to appear at all. I've seen you ask elsewhere for people to confirm whether Radeon's work at all, happy to report they do, with the above caveat, of course.
Cheers
Posted 26 February 2020 - 08:55 AM
It should be compatible with VPX10.6, although it contains some updated vbs scripts compared to the release before, but I'm not sure if they are part of 10.6 or came later. I chose the 0.7 postfix because it is based on the (almost) latest VPX 10.7 commits, but since VR is still more or less a development project I thought 0.7 would be more honest than 10.7. I also decided to upload a separate file, in case the new version has some ugly bugs I missed and the users still can switch back to the old release.
No it is better not to completely remove VPX, but to integrate VPVR into the same folder The 32/64bit version should match your VPX and Pinmame version. VPX should always be in the same folder since VPVR has still no own installer and VPX also helps a lot to narrow down techical issues (First two questions if VPVR is not working are always: do the 32/64bit versions match and is VPX working?).
Since RGBA 16F works fine for Geforce and Radeon users, I think I should set it as default value for the next release.
Posted 26 February 2020 - 02:47 PM
Physics changes? Interesting. Would love to hear about them, but understand if you'd like to keep them under your hat for now, Toxie.
Nothing spectacular. I did some experiments with Embree, as this now features collision detection routines, and thus needed to change some stuff and clean up things under the hood to make that work.
But turns out, that Embree can for some tables even be slower than our quad/kd-tree implementations (as these have more top level information and are also pretty well optimized).
Apart from that i (once again) try to unify more of the physics code. But it's a bottomless pit.
But at least it looks like some tweaks may survive that will improve corner cases and have less issues.
Posted 26 February 2020 - 04:11 PM
Posted 26 February 2020 - 05:24 PM
Physics changes? Interesting. Would love to hear about them, but understand if you'd like to keep them under your hat for now, Toxie.
Nothing spectacular. I did some experiments with Embree, as this now features collision detection routines, and thus needed to change some stuff and clean up things under the hood to make that work.
But turns out, that Embree can for some tables even be slower than our quad/kd-tree implementations (as these have more top level information and are also pretty well optimized).
Apart from that i (once again) try to unify more of the physics code. But it's a bottomless pit.
But at least it looks like some tweaks may survive that will improve corner cases and have less issues.
Embree is R3987 and I only updated to R3986. So VPVR is already outdated again.
Posted 26 February 2020 - 09:39 PM
Yeah, this is one of the reasons I had been holding off bringing VPVR up to date myself - VPX 10.7 has been in a fairly unstable state since Fuzzel began some UI reworkings. I was going to re-visit it once VPX enters its public beta stage, which is usually an indication from them that they feel it's in a usable state.
Good to hear you were able to get it current though! Cheers!