4027 replies to this topic

[DarlimJ]

So I'm rocking over here like it's 2020!  Lol.

 

Beta 112 seems very solid for me with the plunger and software running.
That plunger software can be downloaded for free on the VirtuaPin website.

I can't believe I installed and reinstalled Windows10 and run Baller multiples times only to find out I needed an older exe file.  LOL!

 

Regardless, I'm back selecting and playing tables in Popper and VPX seemingly  without issue.

Woot!  Cheers!

Edited by DarlimJ, 18 August 2022 - 05:23 PM.

[Gravy]

So I'm rocking over here like it's 2020!  Lol.

 

Beta 112 seems very solid for me with the plunger and software running.
That plunger software can be downloaded for free on the VirtuaPin website.

I can't believe I installed and reinstalled Windows10 and run Baller multiples times only to find out I needed an older exe file.  LOL!

 

Regardless, I'm back selecting and playing tables in Popper and VPX seemingly  without issue.

Woot!  Cheers!

If I understand him correctly, I think Toxie would be keen on you updating to newer build numbers incrementally so he can see at what release number the bug rears it's head for you, then he can better detect where the problem may have started. Otherwise you may end up not being able to update in the future if the problem still persists.

You will probably be a bit hesitant to do that as it's working for you now with the older version but ultimately it will help you and anyone else with the issue if he can fix it.

[wiesshund]

 

So I'm rocking over here like it's 2020!  Lol.

 

Beta 112 seems very solid for me with the plunger and software running.
That plunger software can be downloaded for free on the VirtuaPin website.

I can't believe I installed and reinstalled Windows10 and run Baller multiples times only to find out I needed an older exe file.  LOL!

 

Regardless, I'm back selecting and playing tables in Popper and VPX seemingly  without issue.

Woot!  Cheers!

If I understand him correctly, I think Toxie would be keen on you updating to newer build numbers incrementally so he can see at what release number the bug rears it's head for you, then he can better detect where the problem may have started. Otherwise you may end up not being able to update in the future if the problem still persists.

You will probably be a bit hesitant to do that as it's working for you now with the older version but ultimately it will help you and anyone else with the issue if he can fix it.

 

And the easiest way to do that is (this will seem backwards)
Update to the lastest BUT rename the exe to vpx-version_number.exe
fails, log number

Grab next down, but only grab the exe out of the zip (as you already have newest scripts)
Run Die, record version

Repeat until run die stops, then you know which build brought in the issue
report that to Toxie
Continue enjoying running the working Visual PinballX.exe that you left alone the entire time

 

That is what i have done in the past to track down which change brought in an issue, goes pretty fast.
 

[DarlimJ]

Guys, I'm so sorry but I don't have the patience or bandwidth this week to start testing again.

 

It's been... vexing.

Would just like to play and enjoy for a while.

 

Down the road, if I have to install Windows and Baller again with a big updates, I'll happily do that.
I'd like to go to Windows 11.  But that's another story.  No rush.

I do have videos documenting the issue to share if that's at all helpful.

Cheers! 

[wiesshund]

Guys, I'm so sorry but I don't have the patience or bandwidth this week to start testing again.

 

 

I do have videos documenting the issue to share if that's at all helpful.
 

 

Unfortunately, videos do not do much to help, not for this kind of issue.

The only things that a noncoder can really do, is donate the time and effort to test what they can, and document.
In this particular case, documenting in what version did the change causing the issue take place.

 

Not picking on the fact that you dont have time, just stating the simple facts.
It is the only way to help and participate in beta testing, for someone that cannot go looking at things from a source code aspect.
And time it does take, sometimes quite a bit of it, but it is the only way to narrow down when did the issue come in
and in what situation or environments does it occur in.

[DarlimJ]

This is my first time on any beta thread.

 

But I hear you.

At the same time, we can all only do what we can, when we can.

Not about, "not having time."

 

I've contributed in different ways over the last two+ years.

 

I still have some other small issues to sort out over here.
And I haven't touched FP because it just looks like another potential headache to me. 

Nor have I set up FX3 on this new pc.

My son enjoys FX3 so I need to get that back.

Many thanks for all your support recently.
One exe file.  SMH.  Holy Moses,  I pulled out a lot of hair over that one for a good while.  LOL!

Cheers.

[toxie]

Nevertheless, would help if you could find the version that breaks things for you. And its really simple, shouldn't take you more than 10mins overall. Its just 6 beta versions after v112 that are interesting: https://github.com/v...inball/releases

 

Just dload each, extract just the exe, rename it with the number (187,196,etc), click on each, done. 

https://github.com/v...ase-win-x86.zip

https://github.com/v...ase-win-x86.zip

https://github.com/v...ase-win-x86.zip

https://github.com/v...ase-win-x86.zip

https://github.com/v...ase-win-x86.zip

https://github.com/v...ase-win-x86.zip

[wiesshund]

 

And I haven't touched FP because it just looks like another potential headache to me. 

 

 

I can not answer for FX3 as i do not have it
FP is overall, pretty easy
Install the official FP installer
Install the official BAM installer (i install it inside the FP folder, in a folder called.... BAM   yea fine not original)
make a shortcut to BAM's fploader.exe in the FP folder
make a folder inside FP and name it dmdext, drop dmd.exe in it, a copy of dmddevice.ini, and drop the opengl32.dll in the main fp folder

make a bat file named startDMD.bat in the fp folder, put into it
 

cd dmdext
start /min ""  "dmdext.exe" mirror --source=futurepinball -q --virtual-stay-on-top --fps 60 --use-ini="C:\emulation\Future Pinball\dmdext\DmdDevice.ini"

ok, now run your startDMD.bat, and drag the DMD box over to your third screen (if LCD of course)
now run fploader, and pick a table to play

 

that should produce a perfectly running installation to take a look at FP with

Yes, you will want to automate it all via your front end, and that is not hard, but this gives you a starting point.

PUP you already have installed
You would want DOFlinx and PinEvent most likely

But that gives you a starting point to check out some FP table (May i recommend Pink Floyd and GalaGa Pinball (1.1) and Martians (2.0) those should all run without doflinx etc and are fun tables to try out)

 

Terryred can square you away on everything beyond the basic install

[Thalamus]

Nevertheless, would help if you could find the version that breaks things for you. And its really simple, shouldn't take you more than 10mins overall. Its just 6 beta versions after v112 that are interesting: https://github.com/v...inball/releases

 

Just dload each, extract just the exe, rename it with the number (187,196,etc), click on each, done. 

https://github.com/v...ase-win-x86.zip

https://github.com/v...ase-win-x86.zip

https://github.com/v...ase-win-x86.zip

https://github.com/v...ase-win-x86.zip

https://github.com/v...ase-win-x86.zip

https://github.com/v...ase-win-x86.zip

 

I will take a stab at this through the weekend. I want to add. It is not something that happens all the time; so, just running the release - once, is far from enough. Got time though, have some tables I'm fiddling with so ...
 

[studlygoorite]

 I have been updating to every VPVR build that comes out and all of a sudden both my VPinballX_GL.exe and VPinballX.exe now open without having to drag open the right and left sides of the edit box (they stay open). It was suggested that I delete a registry key and that worked for my VPinballX.exe until I started VPVR, after launching the VPinballX_GL.exe both edit boxes would open with the sides closed again. So it looks like maybe it was something to do with the VPinballX_GL.exe that was causing my .exes to not open properly as that's all that I had changed. Maybe hell who knows, maybe something changed with my windows 10 but I think it was the updated VPVR, just an FYI and a thanks.

I'd like to help test the issue above but I am not having it, but what I do have (even with VPX v236) is that I can only play one table launching with the VPinballX.exe, closing the table and trying to launch another with result in VPX hanging and having to force close with task manager, a while back I was able to open several tables one after the other but that did not last long (could be my system). My VPinballX_GL.exe can launch one table after the other and I have no issues running multiple tables one after the other with Popper

[DarlimJ]

***EDITED***

Forgot to mention that on this rig v112 also opens the UI faster, launches tables faster, and PUPs close properly without DMD underlays sticking around often.  Phew.


Leaving town for the weekend but none of these exe(s) are as "snappy" or load tables as fast or faster than 112 over here;

12th gen i7, 3080, 64g ram, 2t ssd. 

 

Happy to do some testing next week and report which ones I need to launch two or three times to open the UI while multiple copies are running in task manager.

 

Thanks for understanding,

joshua

Edited by DarlimJ, 20 August 2022 - 02:56 AM.

[wiesshund]

 

 

 

I will take a stab at this through the weekend. I want to add. It is not something that happens all the time; so, just running the release - once, is far from enough. Got time though, have some tables I'm fiddling with so ...
 

 

 

hehe just save before launching, a lot, hate to see you replicate yourself right out of some editing

[Thalamus]

Seems to be related to changes between 162 and 173. If anyone have builds between these versions avail - I could maybe narrow it down even closer.

 

https://github.com/v...ment-1221296858

[wiesshund]

Seems to be related to changes between 162 and 173. If anyone have builds between these versions avail - I could maybe narrow it down even closer.

 

https://github.com/v...ment-1221296858

I got ya, hang on a minute or 3

https://drive.google...iew?usp=sharing

all builds between 162 and 173
No 172 build, the build failed and skipped to 173

[Thalamus]

Thanks @wiesshund !

 

Since this is intermittent, I can't give a 100% guarantee. But, from my tests. I was able to hang 167, actually on the first try. Ran 166 a lot ... not being able. Went a bit back and forth between those, and 167 would work a few times in a row, but also hang at times. Was NOT able to make 166 hang at all in at least 50 startups. Same test scenario as mentioned on github. Putting the exe into a 221 install. So, yeah, I expect that the issue is related to changes going from 166 to 167.

Edited by Thalamus, 20 August 2022 - 09:15 PM.

[wiesshund]

166 slightly optimize edge insertion

 

167 patch by Arconovum/Hanzoverfist: add GLES parameter to command line t…vpinball #399: Commit d445b3e pushed by toxieainc

 

 

patch by Arconovum/Hanzoverfist: add GLES parameter to command line t… · vpinball/vpinball@d445b3e (github.com)
 

to see the DIFF

Looks like some OpenGL things added, to keep inline with vpxVR i am guessing?

 

Looks like a very small addition
but dont take my word for that, since i am not a coder, 29 lines could very well be something huge

[Halen]

Ok I have problem to import POV from the tables. The message is: Error parsing POV XML file. I have the latest  VPinballX-10.7.1-255-00f2e55-Release-win-x8. I test with VPinballX-10.7.1-221-fbb8a02-Release-win-x86 and is working.

Edited by Halen, 30 August 2022 - 11:46 AM.

[Thalamus]

Wild guess. You are trying to import a pov that has "more than" the old format. Recently it seem to include physics as well. I guess one can argue - POV isn't just POV anymore.

Edited by Thalamus, 30 August 2022 - 01:43 PM.

[Halen]

You are right. Pov is no longer POV. I saw this now.

[wiesshund]

Ok I have problem to import POV from the tables. The message is: Error parsing POV XML file. I have the latest  VPinballX-10.7.1-255-00f2e55-Release-win-x8. I test with VPinballX-10.7.1-221-fbb8a02-Release-win-x86 and is working.

 

10.7.1 rev 255
Importing POV from set 2020 made with VPX 10.6.1

POV contents

<?xml version="1.0" encoding="utf-8"?>
<POV>
	<desktop>
		<inclination>62.600040</inclination>
		<fov>50.000000</fov>
		<layback>4.800000</layback>
		<rotation>0.000000</rotation>
		<xscale>1.441996</xscale>
		<yscale>1.441995</yscale>
		<zscale>1.000000</zscale>
		<xoffset>0.000000</xoffset>
		<yoffset>240.397415</yoffset>
		<zoffset>-75.000000</zoffset>
	</desktop>
	<fullscreen>
		<inclination>6.199995</inclination>
		<fov>89.999657</fov>
		<layback>62.600163</layback>
		<rotation>270.000000</rotation>
		<xscale>2.060000</xscale>
		<yscale>2.602027</yscale>
		<zscale>1.000000</zscale>
		<xoffset>6.800011</xoffset>
		<yoffset>0.000000</yoffset>
		<zoffset>400.000000</zoffset>
	</fullscreen>
	<fullsinglescreen>
		<inclination>52.000000</inclination>
		<fov>50.000000</fov>
		<layback>0.000000</layback>
		<rotation>0.000000</rotation>
		<xscale>1.120000</xscale>
		<yscale>1.080000</yscale>
		<zscale>1.000000</zscale>
		<xoffset>0.000000</xoffset>
		<yoffset>35.000000</yoffset>
		<zoffset>-75.000000</zoffset>
	</fullsinglescreen>
</POV>

 

No error on import

 

Export POV FROM rev 255
POV contents

<?xml version="1.0" encoding="utf-8"?>
<POV>
	<desktop>
		<inclination>0.000000 </inclination>
		<fov>0.000000 </fov>
		<layback>0.000000 0</layback>
		<rotation>0.000000</rotation>
		<xscale>0.000000</xscale>
		<yscale>0.000000</yscale>
		<zscale>0.000000</zscale>
		<xoffset>0.000000</xoffset>
		<yoffset>0.000000 </yoffset>
		<zoffset>0.000000 00</zoffset>
	</desktop>
	<fullscreen>
		<inclination>0.000000</inclination>
		<fov>0.000000 </fov>
		<layback>0.000000 </layback>
		<rotation>0.000000 0</rotation>
		<xscale>0.000000</xscale>
		<yscale>0.000000</yscale>
		<zscale>0.000000</zscale>
		<xoffset>0.000000 </xoffset>
		<yoffset>0.000000 </yoffset>
		<zoffset>0.000000 00</zoffset>
	</fullscreen>
	<fullsinglescreen>
		<inclination>0.000000 </inclination>
		<fov>0.000000 </fov>
		<layback>0.000000</layback>
		<rotation>0.000000</rotation>
		<xscale>0.000000</xscale>
		<yscale>0.000000</yscale>
		<zscale>0.000000</zscale>
		<xoffset>0.000000</xoffset>
		<yoffset>0.000000 0</yoffset>
		<zoffset>0.000000 00</zoffset>
	</fullsinglescreen>
	<customsettings>
		<SSAA> 0</SSAA>
		<postprocAA> 0</postprocAA>
		<ingameAO> 0</ingameAO>
		<ScSpReflect> 0</ScSpReflect>
		<FPSLimiter> 0</FPSLimiter>
		<OverwriteDetailsLevel> </OverwriteDetailsLevel>
		<DetailsLevel> 0</DetailsLevel>
		<BallReflection> 0</BallReflection>
		<BallTrail> 0</BallTrail>
		<BallTrailStrength>0.000000</BallTrailStrength>
		<OverwriteNightDay> </OverwriteNightDay>
		<NightDayLevel> 0</NightDayLevel>
		<GameplayDifficulty>0.000000</GameplayDifficulty>
		<PhysicsSet> </PhysicsSet>
		<IncludeFlipperPhysics> </IncludeFlipperPhysics>
		<SoundVolume> 00</SoundVolume>
		<MusicVolume> 00</MusicVolume>
	</customsettings>
</POV>

What this does not show as the forum can not show it aside from some null space, is this

 

It is not a problem Importing
It is a problem that the export has at some point become corrupted

 

This POV can not be imported at all.

 

The proper POV format is
 

<?xml version="1.0" encoding="utf-8"?>
<POV>
	<desktop>
		<inclination>46.000023</inclination>
		<fov>45.000000</fov>
		<layback>-10.399995</layback>
		<rotation>0.000000</rotation>
		<xscale>1.000000</xscale>
		<yscale>1.000000</yscale>
		<zscale>1.000000</zscale>
		<xoffset>0.000000</xoffset>
		<yoffset>30.600048</yoffset>
		<zoffset>-610.000000</zoffset>
	</desktop>
	<fullscreen>
		<inclination>5.000000</inclination>
		<fov>35.600021</fov>
		<layback>48.000000</layback>
		<rotation>270.000000</rotation>
		<xscale>0.897600</xscale>
		<yscale>1.080000</yscale>
		<zscale>1.000000</zscale>
		<xoffset>-6.500000</xoffset>
		<yoffset>-0.000000</yoffset>
		<zoffset>-300.000000</zoffset>
	</fullscreen>
	<fullsinglescreen>
		<inclination>37.000000</inclination>
		<fov>47.000000</fov>
		<layback>0.000000</layback>
		<rotation>0.000000</rotation>
		<xscale>1.000000</xscale>
		<yscale>1.000000</yscale>
		<zscale>1.000000</zscale>
		<xoffset>0.000000</xoffset>
		<yoffset>-20.000000</yoffset>
		<zoffset>-200.000000</zoffset>
	</fullsinglescreen>
	<customsettings>
		<SSAA>-1</SSAA>
		<postprocAA>-1</postprocAA>
		<ingameAO>-1</ingameAO>
		<ScSpReflect>-1</ScSpReflect>
		<FPSLimiter>-1</FPSLimiter>
		<OverwriteDetailsLevel>1</OverwriteDetailsLevel>
		<DetailsLevel>10</DetailsLevel>
		<BallReflection>-1</BallReflection>
		<BallTrail>-1</BallTrail>
		<BallTrailStrength>0.392157</BallTrailStrength>
		<OverwriteNightDay>1</OverwriteNightDay>
		<NightDayLevel>14</NightDayLevel>
		<GameplayDifficulty>0.000000</GameplayDifficulty>
		<PhysicsSet>0</PhysicsSet>
		<IncludeFlipperPhysics>0</IncludeFlipperPhysics>
		<SoundVolume>100</SoundVolume>
		<MusicVolume>100</MusicVolume>
	</customsettings>
</POV>

The break happens in REV 228

use string literals for loads/saves and defines for the regKey

vpinball #451

 

 

https://github.com/v...a18daa9e946758e

Bug ticket filed

Exported DATA such as POV's is corrupt beginning at revision 228 · Issue #97 · vpinball/vpinball (github.com)