616 replies to this topic

[Joppnl]

OK...installed the final 10.3 version but I do notice a problem within the F6 camera mode.

 

With the flipperbuttons I can change the value of the current parameter (starting with inclination) but with the magnasave buttons it is not possible (anymore) to change/walk through the parameters

 

It did work with previous (latest 10.2) version I used.

 

I double checked the keys-settings options in VPX and redifined my magna save buttons but they are ok and it didn't solve it.

 

The magna save buttons do change however the X-Y-Z point of view. 

 

So, this is for me a kind of problem as I'm not able to change the X-Y scale and position anymore. And when holding the flipperbutton to change the value the value change is very very very fast. To fast to make it exact.

 

Could you pls have a look at these 2 points?

 

Thank you!

[toxie]

what are the magna buttons mapped to?

[Outhere]

I had my flipper and Magnum buttons map to the arrow keys and it worked with the camera mode in the VP10.2.1

But in VP10.3 - It would move the screen up down left and right real fast that's all it did...
I remap them to the controller and shift keys to get the camera mode to work correctly

Edited by Outhere, 15 June 2017 - 02:26 PM.

[toxie]

Yeah, the arrow keys are now hardwired to movement due to the patch that Hanzoverfist introduced..

[Joppnl]

what are the magna buttons mapped to?

 

I assigned them to the letters W (left) and S (right) as my keywiz controller standard definition are these letters for these 2 switches.

 

But  as far as my programming knowledge goes, it should not be importent which value is attached to the nudge buttons: the software itself should say "nudge-L /R"and it's the user who defines it within VPX what keys are connected to the nudge buttons (don't know how to make it clearer but I think this should be the case and that is how it previously was... just my non-experience programming thoughts  :- ) 

 

Thank you for your support!

 

Edited by Joppnl, 15 June 2017 - 07:31 PM.

[BorgDog]

Yeah, the arrow keys are now hardwired to movement due to the patch that Hanzoverfist introduced..

@toxie Any chance to make that not hard-wired, add to the chart of ones so we can set it to whatever works for us?

[BananaBoat]

Thanks Toxie...ill take a read.
Cheers

Sent from my SM-G935F using Tapatalk

[RogerRoger]

I just upgraded from 10.1 to 10.3, not having tried any of the betas. There seems to be an increase in elasticity in playfield objects. I've tried out a few tables to be certain it isn't just one. They are all much "bouncier" and generally more difficult.

 

Edit: After playing more tables, the trend seems to show the newer VPX tables have more elasticity in the objects, whereas the older VPX tables play more or less the same. The newer ones happen to be tables I haven't done much or any object editing in yet. Guess these newer tables may need changes too now.

Edited by RogerRoger, 17 June 2017 - 05:03 PM.

[fuzzel]

Yeah, the arrow keys are now hardwired to movement due to the patch that Hanzoverfist introduced..

@toxie Any chance to make that not hard-wired, add to the chart of ones so we can set it to whatever works for us?

W can change that in 10.4 yes

[STV]

Hi, I only just noticed the vpinball994.exe included in the new release.   Should we repoint anything using vpinball992.exe  to this new 994, is that the idea?  

[wrd1972]

Ive got a weird issue with standard VP9 (994) and the tables not starting when "button 9" is pressed on the cab. This is based off of the VP executable provided in the official 10.3 installer release. Problem also occurs on 921 and 993.

 

I have confirmed that that VP9 PM executable will start tables...as well as VP10. But standard VP9 simply wont start the table when button 9 is pressed but all of the other fuctions EG: add coing, flippers etc work perfectl.

 

I have also confirmed that cab button mappings are identical in VP9, VP-PM and VP10 on my cab. So I dont think its anything on my end...but could be wrong but I just cant figure out why.

 

Any idea whats going on here?

Thanks

Edited by wrd1972, 17 June 2017 - 07:46 PM.

[toxie]

Hi, I only just noticed the vpinball994.exe included in the new release.   Should we repoint anything using vpinball992.exe  to this new 994, is that the idea?  

 

yes.. but as the VP9 releases are not so well tested, i decided to give new names there instead of using a single VPinball9.exe all the time (but the newer versions should all be fine, as only minimal changes went into these anyway)..

 

same for the new PM5 build in there..

[STV]

Ok, got it.  Thanks. 

 

Two casualties with the new pm5 so far.  Is there a 10.4 beta thread for bugreports? 

 

Batman the dark knight - a full strength plunger sends the ball into hyperspace.  You see it shoot off and it disappears.  You can keep the ball on the playfield with a less than full plunge.

 

Cyclone - after the ball is in the trough for launching, nudge the table and the ball will fall right out.  As if it fell into a hole.  Just disappears. 

 

Verified with the 8-20-2014 pm5 build I can't make this happen.

[chepas]

Anyone know why I would get a "machine terminated before initialized" when set to exlusive full screen?

 

Any table with pinmame it doesn't like, but they work in window fullscreen.

[Thalamus]

Compare registry for a working table vs a problem one - I believe ddraw might be the culprit.

[chepas]

Yes that was it, thanks. Didn't compare, just went straight to registry, search for romname, set the ddraw to 0.

Edited by chepas, 17 June 2017 - 11:28 PM.

[toxie]

 

Ok, got it.  Thanks. 

 

Two casualties with the new pm5 so far.  Is there a 10.4 beta thread for bugreports? 

 

Batman the dark knight - a full strength plunger sends the ball into hyperspace.  You see it shoot off and it disappears.  You can keep the ball on the playfield with a less than full plunge.

 

Cyclone - after the ball is in the trough for launching, nudge the table and the ball will fall right out.  As if it fell into a hole.  Just disappears. 

 

Verified with the 8-20-2014 pm5 build I can't make this happen.

 

 

the first one is due to the new plunger code, set in the plunger's state: enable mech plunger. that was the solution, i think..

the second could be the same issue, don't know..

[wrd1972]

Toxie,

When you have a moment. Would you please speak to the issue I posted 7 replies back? It really feels like a serious bug for the cab guys.

 

Thanks

Edited by wrd1972, 18 June 2017 - 03:54 PM.

[chepas]

Another weird bug I'm getting someone may know about....Not being able to see the script editor?

 

It's open but all you can do is hover over task bar which shows a tansparent script window.

[toxie]

Toxie,

When you have a moment. Would you please speak to the issue I posted 7 replies back? It really feels like a serious bug for the cab guys.

 

When i compare/diff all the input code of PM5 vs VP9.9.4, then i do not see any notable differences that could cause this.   :/

Another weird bug I'm getting someone may know about....Not being able to see the script editor?

 

It's open but all you can do is hover over task bar which shows a tansparent script window.

 

Do you have a screenshot, please?