4027 replies to this topic

[Thalamus]

Though I don't recommend it for everyone. Register an account on github.com. Once that is fixed, go to the Actions tab on top of the VPinball repo. https://github.com/v...pinball/actions

Now pick what build you want. The newest is on top. Currently it is "NULL -> nullptr ...." - once pressed, scroll down to the very bottom. There you find the different builds. 99.9% of us wants the "VPinballX-10.7.0-323-6bb382b-Release-win-x86 " build. If you've got issues, then the Debug would be nice to run to help the devs out.

[BleedinFingers]

Thanks Thalamus, I got 323 now with debug and it is the same. I open a blank table run it and it shows "Visual Pinball" in the textbox, open the font dialog, don't even change anything and run again and the text vanishes. I all really happy to try helping rather than just reporting an issue, does the debug version log somewhere as I cant find where

[BleedinFingers]

Thanks Thalamus, I got 323 now with debug and it is the same. I open a blank table run it and it shows "Visual Pinball" in the textbox, open the font dialog, don't even change anything and run again and the text vanishes. I all really happy to try helping rather than just reporting an issue, does the debug version log somewhere as I cant find where

 

I have also confirmed the same behavior on my cab with a very early version of 10.7 (in Test Desktop mode of course)

[Thalamus]

Debug version is supposed to be able to tell when VPX crashes, the line number where it crashes, for what I read. Not very useful for your "not working", issue. I expect that debug might in some cases work slightly slower than the one without, which is what you should run until you get instabilities and "pure" crashes. That is when you download the debug and run it, but, it MUST be from the same build.

[wiesshund]

Debug version is supposed to be able to tell when VPX crashes, the line number where it crashes, for what I read. Not very useful for your "not working", issue. I expect that debug might in some cases work slightly slower than the one without, which is what you should run until you get instabilities and "pure" crashes. That is when you download the debug and run it, but, it MUST be from the same build.

Debug not going to help here, he is right, there is a bug in how ever it is saving the info for the text box

 

File > new > Blank Table

Create new text box named test

add to script

test.text= "I am a text display box   "

 

run table
box works

 

quit to editor

 

Change font on box (does not matter which font is picked)

run table
font is about 2point in size

 

quit to editor

change font size for box
run table, font is still 2 point

 

Delete box, add new box test2

edit script

test2.text= "I am another text display box   "

Run table

box works

quit to editor

change font size, does not matter what size, pick any

run table

font is now 2point

 

save table exit and reload vpx

font is still 2 point

 

Do anything to font in text box and display becomes broken size wise
the new font does display, you can change color etc, but the font size will be about 2 point and nothing will make it bigger

 

Nothing crashes, it all works fine aside from the fact you can not read a 2point font and you can not make it bigger

 

Seems to be an issue even in 10.6?

Textbox not honoring font size that I set - VP Help Center - VPForums.org

 

So i tried it in 10.6.2

Some times it would not save the font size change properly, but it never made it become 2point
it would frequently refuse to change the font type and you had to smack it a few times
but it did not debase the font into an unreadable 2point blur

[BleedinFingers]

Don't know if this will help the devs as my C++ is 25years rusty, but it seems to be working for decals. Looking at the source

 

decal.cpp

   bw.WriteTag(FID(FONT));

   IPersistStream * ips;

   m_pIFont->QueryInterface(IID_IPersistStream, (void **)&ips);

   ips->Save(pstm, TRUE);

 

textbox.cpp

   bw.WriteTag(FID(FONT));

   IPersistStream * ips;

   m_pIFont->QueryInterface(IID_IPersistStream, (void **)&ips);

   HRESULT hr;

   hr = ips->Save(pstm, TRUE);

[kiwi]

@CommandReference

 

In the properties of the kicker, the method of how to change the image and color of the ball is missing.

CreateBall.Image
CreateBall.Color

 

[wiesshund]

REV 323

 

Analog nudge seems fubar

 

regardless of axis moved, it only nudges up

nudge test table shows axis going in correct direction and amount on the apron indicators

balls though only go up, even when nudging sideways, the balls go up.

 

load same nudge test table in 10.6.2
balls move where nudge would make them go

Same exact settings nothing changed in prefs at all

 

Even if you crank all the nudge settings way up in 10.7 REV323, the only place the balls go is up
regardless of what way the nudge axis is going

 

Xinput seems to work so far, at least in basic rudimentary feed back

Dinput i can not properly test as i dod not know how to make it engage all the possible feed back channels in dInput
Xinput is limited to the 2 motors, of which VPX uses only 1 so far at a fixed speed with varying duration, but no wav forms

Dinput on the other hand can have a number of things, for giggles i was going to try it on flight sim controls which have 2 vibrators and 4 stepper motors and several lamps
but i am not even sure how to try

[NailBuster]

small-ish vpx issue but will come up a lot i'm sure.

 

if you have any pop-out editor/property windows in v10.7,  vpx will still show them in front-end during loading when vpx is ran with minimized parameter.

 

to clarify.  if you run vpx -minimized then the main vpx editor will properly be minimized/hidden on loading table... but if you have any pop-out editor windows they will not be hidden like the main vpx editor (will always show).  Workaround currently is to not use pop-out editor windows in v10.7.

[wiesshund]

small-ish vpx issue but will come up a lot i'm sure.

 

if you have any pop-out editor/property windows in v10.7,  vpx will still show them in front-end during loading when vpx is ran with minimized parameter.

 

to clarify.  if you run vpx -minimized then the main vpx editor will properly be minimized/hidden on loading table... but if you have any pop-out editor windows they will not be hidden like the main vpx editor (will always show).  Workaround currently is to not use pop-out editor windows in v10.7.

Yes, even not on popper, if i have the tool panel, properties panel and layers panel undocked, then when i launch, they will appear on the backglass screen until the B2S loads
over top of the loading animation

 

If i redock them, then they do not appear
Not a problem for most cab users, but for those who might be doing editing at a cab or cab like setup, it may be a wee bit annoying
(Cause flipping the OS and then building the table in a full cab view with tool panels on the backglass is great actually)

[Thalamus]

Maybe it would be a good idea to make a small button or something, and a param that would force the dock panels into fixed standard positions ? I don't have problems with them, but, seen a few guys asking.

[jejepinball]

Don't know if known issue. Editor > BackglassView > Create Decal > Set size = width or height

 

The decal element doesn't update in the editor. You have to start a game, quit, then select the decal again for Editor UI to update.

 

For information, this bug still exists in 10.7 rev310.

[wiesshund]

 

Don't know if known issue. Editor > BackglassView > Create Decal > Set size = width or height

 

The decal element doesn't update in the editor. You have to start a game, quit, then select the decal again for Editor UI to update.

 

For information, this bug still exists in 10.7 rev310.

 

Latest is REV 323 and it still exists there

[freebird1963]

Can this go on its own or does it get copied over the previous install. ? 

Yea newbie , smell the shrink wrap on me. :-)  (Marine saying for new recruits)

Semper Fi

[wiesshund]

Can this go on its own or does it get copied over the previous install. ? 

Yea newbie , smell the shrink wrap on me. :-)  (Marine saying for new recruits)

Semper Fi

go into your existing VPX folder, rename VpinballX.exe to VpinballX 10.6.exe

(so you have it as backup)

Then unzip 10.7 into your existing folder and allow the file overwrites

[wiesshund]

@Toxie @Fuzzel

When you guys have time, can you come and read over the last few pages of this thread?

https://www.vpforums...e=4#entry488524

 

We have determined a cause or trigger for the Radeon 6000 series rendering issues
we have figured out how to replicate it and how to make it go away but the making it go away is not really a fix
but do not know where to go from here

[fripounet]

pouvons-nous pivoter la pf de 180° , pour dévoiler un 2e jeu ?

 pf1 : jeu subtil de précision (style EM)

pf2 : jeu gros bourrin (with ramp) pour multiball 

 

 

trad. Google 

can we rotate the pf 180 °, to reveal a 2nd set?

  pf1: subtle game of precision

pf2: big nag game for multiball

Edited by fripounet, 15 October 2021 - 10:05 AM.

[jpsalas]

The playfield graphic is redrawn at the start of the table and it can't be changed later. But you can always use a primitive or two, or a ramp or two and make them visible/invisible.

[StimpyX]

Posted this on the discord, but also trying here...

 

Having a weird issue with vpx 10.7. Whenever I try to run it, the application screen flickers as if it is trying to open the 'select table' screen and all I can do is force quit it. Anyone having this issue? I'm running the 32bit version on Windows 11. 10.6 runs fine.

 

example:

https://media.giphy....bT76M/giphy.gif

 

(Wont let me post the gif of app)

[wiesshund]