4027 replies to this topic

[Halen]

wiesshund

 

You are the man!!!!!!!!!

[wiesshund]

wiesshund

 

You are the man!!!!!!!!!

 

I aint fixed nothing, just pointed the finger at the condemned
 

[toxie]

Rightfully so. 

 

But its fixed now again. Thanks wiesshund (and all the other brave testers), as usual!

[freebird1963]

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

So just to clarify to test these things we just need the vpinball.exe not all the other files and scripts ? 

[Thalamus]

Basically - yes, as long as you're already on the 10.7.x series.

Edited by Thalamus, 30 August 2022 - 10:06 PM.

[wiesshund]

 

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

So just to clarify to test these things we just need the vpinball.exe not all the other files and scripts ? 

 

 

It is a yes/no answer
when no scripts have changed, and/or it is a non script issue being investigated then yes only the EXE would be needed
 

Sometimes the answer could be no
if an issue is tied to one of the scripts
Or also, if an issue is tied to a new DLL, like if a new bass.dll comes out

 

the issue toxie's post pertained to though, that one was all EXE
as is the one above i tested

[lukpcn]

Wouldn't it be better to have a .pov file with previous pov settings and .phy file (or any other name like .cfg maybe or something) with other settings ? and import/export/read them as separate things ? this way there is a backward compatibility - just a thought.

Edited by lukpcn, 31 August 2022 - 11:39 AM.

[wiesshund]

Wouldn't it be better to have a .pov file with previous pov settings and .phy file (or any other name like .cfg maybe or something) with other settings ? and import/export/read them as separate things ? this way there is a backward compatibility - just a thought.

the POV's are backwards compatible, they have all of the previous settings

though i can not really see anyone exporting a POV and then going and trying to use it in vpx 10.5 or something
if they have 10.7.x to begin with.

[lukpcn]

 

Wouldn't it be better to have a .pov file with previous pov settings and .phy file (or any other name like .cfg maybe or something) with other settings ? and import/export/read them as separate things ? this way there is a backward compatibility - just a thought.

the POV's are backwards compatible, they have all of the previous settings

though i can not really see anyone exporting a POV and then going and trying to use it in vpx 10.5 or something
if they have 10.7.x to begin with.

 

Fair enough

[freebird1963]

Okay gotta ask this cuz I haven't done anything else but d/l the rel 215 and 222 and run the exes.

Since doing that I lost my HV BItpixel output. Nothing showing up. F1 shows cabinet dmd unchecked and USe External DMD checked. And sometimes now I'm seeing both the cabinet dmd scoring and External dmd. Couple tables they are covering up the monitor under the playfield. I can't think of what else to try or loo at and all I have done differently was run those two exe's. Tho I can't think why that should have caused a issue.

*sigh *

[wiesshund]

Okay gotta ask this cuz I haven't done anything else but d/l the rel 215 and 222 and run the exes.

Since doing that I lost my HV BItpixel output. Nothing showing up. F1 shows cabinet dmd unchecked and USe External DMD checked. And sometimes now I'm seeing both the cabinet dmd scoring and External dmd. Couple tables they are covering up the monitor under the playfield. I can't think of what else to try or loo at and all I have done differently was run those two exe's. Tho I can't think why that should have caused a issue.

*sigh *

 

Revision 258 is the latestet 215 and 222 are old

I do not know what an HV Bitpixel is, but it looks like you are pointing at a Vpinmame / dmdextensions issue rather than vpx itself?
but not sure, might try a current revision 1st

[freebird1963]

 

Okay gotta ask this cuz I haven't done anything else but d/l the rel 215 and 222 and run the exes.

Since doing that I lost my HV BItpixel output. Nothing showing up. F1 shows cabinet dmd unchecked and USe External DMD checked. And sometimes now I'm seeing both the cabinet dmd scoring and External dmd. Couple tables they are covering up the monitor under the playfield. I can't think of what else to try or loo at and all I have done differently was run those two exe's. Tho I can't think why that should have caused a issue.

*sigh *

 

Revision 258 is the latestet 215 and 222 are old

I do not know what an HV Bitpixel is, but it looks like you are pointing at a Vpinmame / dmdextensions issue rather than vpx itself?
but not sure, might try a current revision 1st

 

Not sure how or why or by what or who but seems my dmddevice.ini got changed. The Pixelcade section was missing a part - enabled = true.

Sad part is I looked at it like 3 times and didn't notice it any of those times. Maybe cuz dmdext.ini had it and got my self going in circles trying to track it down.

As for the rev it was what ever was in Toxie's post from a couple days ago were I asked about if the exe's were all that had to be copied for exes testing and I dont recall exact rev numbers but those are whats burnt in my mem cells.

Off to screw something else up (so it seems lately)

[wiesshund]

 

 

Okay gotta ask this cuz I haven't done anything else but d/l the rel 215 and 222 and run the exes.

Since doing that I lost my HV BItpixel output. Nothing showing up. F1 shows cabinet dmd unchecked and USe External DMD checked. And sometimes now I'm seeing both the cabinet dmd scoring and External dmd. Couple tables they are covering up the monitor under the playfield. I can't think of what else to try or loo at and all I have done differently was run those two exe's. Tho I can't think why that should have caused a issue.

*sigh *

 

Revision 258 is the latestet 215 and 222 are old

I do not know what an HV Bitpixel is, but it looks like you are pointing at a Vpinmame / dmdextensions issue rather than vpx itself?
but not sure, might try a current revision 1st

 

Not sure how or why or by what or who but seems my dmddevice.ini got changed. The Pixelcade section was missing a part - enabled = true.

Sad part is I looked at it like 3 times and didn't notice it any of those times. Maybe cuz dmdext.ini had it and got my self going in circles trying to track it down.

As for the rev it was what ever was in Toxie's post from a couple days ago were I asked about if the exe's were all that had to be copied for exes testing and I dont recall exact rev numbers but those are whats burnt in my mem cells.

Off to screw something else up (so it seems lately)

 

 

those exes in that specific post, were for identifying a particular issue
vpx though does not write to dmddevice.ini

only dmdext does as far as i know

 

and updating dmdext will if you copy over the default ini from the zip.

 

the latest revision should be devoid of the POV export bug as well as the vpx not exiting cleanly bug

[Pinballman]

 

Okay gotta ask this cuz I haven't done anything else but d/l the rel 215 and 222 and run the exes.

Since doing that I lost my HV BItpixel output. Nothing showing up. F1 shows cabinet dmd unchecked and USe External DMD checked. And sometimes now I'm seeing both the cabinet dmd scoring and External dmd. Couple tables they are covering up the monitor under the playfield. I can't think of what else to try or loo at and all I have done differently was run those two exe's. Tho I can't think why that should have caused a issue.

*sigh *

 

Revision 258 is the latestet 215 and 222 are old
 

 

Could you please post a link to revision 258?  The latest one I could find on gifthub is 222. Thank you!

[wiesshund]

 

 

Okay gotta ask this cuz I haven't done anything else but d/l the rel 215 and 222 and run the exes.

Since doing that I lost my HV BItpixel output. Nothing showing up. F1 shows cabinet dmd unchecked and USe External DMD checked. And sometimes now I'm seeing both the cabinet dmd scoring and External dmd. Couple tables they are covering up the monitor under the playfield. I can't think of what else to try or loo at and all I have done differently was run those two exe's. Tho I can't think why that should have caused a issue.

*sigh *

 

Revision 258 is the latestet 215 and 222 are old
 

 

Could you please post a link to revision 258?  The latest one I could find on gifthub is 222. Thank you!

 

click actions in github
look for latest successful action

[wiesshund]

@Toxie

in the xinput feedback, is there any way to adjust the intensity?

 

i have noticed that the intensity seems to be pretty light from when you 1st implemented it

can it be manipulated via table script at all?
Or maybe a generic force slider implemented in the prefs panel?

 

Though not many authors would use it
it would be kind of neat if it could be implemented where you could pick a table with script profile, or call it in the table init

and then put some commands in the table itself

 

like

Sub something_hit
xrumble bigmotor, intensity, duration
 

[fuzzel]

after a long time: here is a new beta build 277-30548e4:

 

- update VPX to integrate VPVR. VPVR is not fully supported but we're getting close

- improved camera handling (in camera mode)

- add additive blending mode to primitives (like for flashers)

- light intensity can be checked while playing via script

- fix old wire ramp issue

- fix font size handling 

- code cleanup and memory leak fixes

[toxie]

Please all test. This build is supposed to become the next release. 

 

 

We know that there are still quite some open bugs, but we also want to get this version out the door, before vbousquet will do the final merger with the VPVR codebase at some point (which might be more risky).

Also note that we directly went to 10.7.2, to match the internal fileversion (i.e. avoid confusion for all ppl not following this excessive thread).

@Toxie

in the xinput feedback, is there any way to adjust the intensity?

...

like

Sub something_hit
xrumble bigmotor, intensity, duration
 

Good point! Will do the first thing for sure (globally), don't know about the script though.

[Victor74]

i´m testing  VPinballX-10.7.2-277-30548e4-Release-win-x86.rar

 

Sometimes the tables do not open when double clicking.

By double-clicking for the second or third time, the table finally opens.

If I do Alt+Ctrl+Delete in the task manager, I can see several Visual Pinball processes that have not been closed after closing Visual Pinball.

[mora]

Hello everyone,

I have the VPX_7_beta_rev359_rc version installed, I update to this version and try it, is that right? Congratulations for your great work, I had a great time, thank you, thank you