Jump to content



Photo
* * * * * 18 votes

VP10 is here (beta)

VP10

  • Please log in to reply
3889 replies to this topic

#3821 bassgeige

bassgeige

    Enthusiast

  • Platinum Supporter
  • 409 posts

  • Flag: Germany

  • Favorite Pinball: Enjoyed on a regular basis.

Posted 30 December 2015 - 04:17 PM

Does the 64 bit version avoid a to less RAM warning while the table loads together with the dB2S file after the play request button is used?

 

How can I modify the latest Cirqus Voltaire release from Dozer that it will work? At the moment the script does not work completely.

 

Attached File  invalid controller selected.PNG   24.5KB   18 downloads

Attached File  invalid controller selected_2.PNG   15.67KB   18 downloads

Attached File  invalid controller selected_3.PNG   12.7KB   17 downloads



#3822 fuzzel

fuzzel

    spaghetti code

  • VP Dev Team
  • PipPipPipPipPip
  • 2,818 posts

  • Flag: Germany

  • Favorite Pinball: yes I have

Posted 30 December 2015 - 05:11 PM

It looks like you haven't registered VPM and VPX can't find it.

#3823 bassgeige

bassgeige

    Enthusiast

  • Platinum Supporter
  • 409 posts

  • Flag: Germany

  • Favorite Pinball: Enjoyed on a regular basis.

Posted 30 December 2015 - 06:21 PM

I installed VPinMAME26_Minimal again. The test with cv_20h as ROM is shown and running. The Test with 64 bit (VPX_Experimental_64bit) does still not work for me. The fallback with the saved files bass, FreeImage and SciLexerVP and official VPinballX_Minimal together with the corresponding exe works. It seems I screwed something big up and can not see what it is at the moment.

 

Does registering VPM mean something more than what I did to ensure it works?



#3824 bent98

bent98

    Pinball Fan

  • Members
  • PipPipPipPip
  • 1,077 posts
  • Location:NY

  • Flag: United States of America

  • Favorite Pinball: Roadshow, Haunted House, Safe Cracker

Posted 30 December 2015 - 06:46 PM

  :)


Edited by bent98, 30 December 2015 - 06:47 PM.


#3825 atarian

atarian

    Enthusiast

  • Members
  • PipPipPip
  • 345 posts

  • Flag: France

  • Favorite Pinball: EMs

Posted 30 December 2015 - 08:32 PM

Many thanks for the 64 bit versions of VP and VPinmame. I initially got the same controller error and guessed it was due to me using the B2S Server for the table. By switching to the Pinmame controller it worked great. PinDMD also needs to be switched off I believe (at least for me with a PinDMD1).

Edited by atarian, 30 December 2015 - 08:33 PM.


#3826 bassgeige

bassgeige

    Enthusiast

  • Platinum Supporter
  • 409 posts

  • Flag: Germany

  • Favorite Pinball: Enjoyed on a regular basis.

Posted 30 December 2015 - 10:01 PM

Is VPinMAME26_Minimal the 64 bit release? I am clueless.

 

Attached File  VPinNAME.PNG   16.76KB   17 downloads



#3827 edizzle

edizzle

    Enthusiast

  • Members
  • PipPipPip
  • 259 posts

  • Flag: United States of America

  • Favorite Pinball: Cyclone

Posted 30 December 2015 - 11:02 PM

 

I went back to my cab....

- set my Nvidia to the default (restored) settings (Except for your two exceptions)

- set VP's FPS limiter to "1"

 

I will have to say, I felt my system was pretty smooth... but doing all your settings and making all the other settings were correct.... it is for sure EVEN SMOOTHER .... is it just wishful thinking on my part??... I hope not... I really do feel having all these exact settings has help on the smoothness and shutter free system....Thank You! 

 

I also want to say.... this all being with in one post and not scattered throughout the forum, should help most people get equal results on there systems...

 

anyway will also post my performance tab and compatibility tab... look good?

 

22662221547_1f63d08db9_o_d.png

You're missing the bottom here of the Performance settings in your screen capture and a couple items are missing (one totally key item especially).  I'm assuming even though you can't see it in your capture, that you also have the "Use visual styles on windows and buttons" option selected because if you don't you would not be able to retain your "Enable Desktop Composition" settings and a couple other ones after applying or choosing OK and exiting this screen / tab.  Windows is weird this way as if you don't enable the visual styles option at the bottom, it let's you think that you can enable the Desktop Composition on it's own and shows that box selected, however, when you exit the screen / control panel and come back in, it's cleared.  This does this on both my systems and on my cab I need to have at least a few other items selected to get as thin as possible but still actually allow / enable Desktop Composition.  

 

You should post another shot / capture with the full screen settings (maybe consider even editing the post above) as if someone else is looking at yours as a reference, it can / will be misleading especially if they save it all / apply and think it's all cool, then leave it as is, because of that weird Windows quirk, they won't know that Enable Desktop Composition actually got cleared and not actually enabled (and for that matter a few other Aero options around it go actually missing / no longer show).  Like I say, I'm assuming you have it on as you would not have been able to go into that screen and see that Desktop Composition was actually checked off.  

 

The other key test to verify within VP if you think that you may or may not have Desktop Composition on or not is a pretty clear one - hit F11 during game play and if the stats are flickering, you're not using it (i.e. going to not be getting the smoothest / stutter / hick-up free play possible). You want to see those stats solid and without flicker if you want to be certain you're allowing Desktop Composition / Aero / Windows DWM to be working. 

 

This again is all unfortunately at the expense of a little bit of flipper lag and Desktop Composition would be good to actually be able to disable for this reason if it wasn't for the introduced ball fluidity issues.

 

So I thought I was getting pretty close to getting the setting dialed in.  I have a GTX660, I believe, i5 and 12g of Ram running Win 7.  I have my settings in Win 7, VPX, and NVidia control panel set as hauntfreaks suggested, and was getting good fps and stutter-free gameplay.  With F11 pressed, I did notice that the stats were solid, whereas before I changed the settings they were flickering as HF mentioned.  Well, then I started playing yesterday, and the the stats sporadically started flickering, and I could see the FPS dropping anywhere from down to 45, 30, or even sometimes in the teens.  It really didn't seem to happen during any visually intensive sequence either...but the stutter was very noticeable.  What is also weird..any maybe my setup always did this but I never noticed, but every time the stats on VP started flickering on screen, I could hear a faint sound change coming from my physical vp computer...I still can't quite tell what it is, but it almost like a change in fan rpms...like I said, fain't but audible.  and it coincides exactly with every time the stats start flickering...the flickering only lasts about 1-2 seconds every time it occurs, but it keeps happening and takes away from the game play.

 

I honestly don't know if my setup was doing this prior to yesterday, which is when I upped my ram from 6G to 12G.  But it seems very strange and I don't recall having this sporadic stutter when playing before.  anyone else experiencing this?  For the most part I've only noticed it when playing VPX, though that might be because that's all I've really been playing lately, which of course is AWESOME!



#3828 RYSr

RYSr

    Pinball Fan

  • Charter Member
  • 511 posts
  • Location:Mercerville (Central) NJ, USA

  • Flag: United States of America

  • Favorite Pinball: TZ - G&R - MB - CV - Metallica

Posted 30 December 2015 - 11:18 PM

Edizzle,

 

Are you boosting the CPS on your CPU or Ram or GPU?

I had this happen when the auto boost setting was pushing the system to far, the fans would speedup and the FPS of the table would start dropping to a stand still.

Under normal desktop it was OK but a demanding game caused it to over clock it.

 

Also if you were in the computer adding ram, make sure a cable didn't move or touch and obstruct the GPU or CPU  Fans.

Rich


Edited by RYSr, 30 December 2015 - 11:37 PM.


#3829 edizzle

edizzle

    Enthusiast

  • Members
  • PipPipPip
  • 259 posts

  • Flag: United States of America

  • Favorite Pinball: Cyclone

Posted 31 December 2015 - 12:09 AM

Edizzle,

 

Are you boosting the CPS on your CPU or Ram or GPU?

I had this happen when the auto boost setting was pushing the system to far, the fans would speedup and the FPS of the table would start dropping to a stand still.

Under normal desktop it was OK but a demanding game caused it to over clock it.

 

Also if you were in the computer adding ram, make sure a cable didn't move or touch and obstruct the GPU or CPU  Fans.

Rich

Ahh, interesting information RYSr.  thanks for the response.  If you don't mind, you'll have to pardon me as I'm not overly computer savvy.  If I am boosting the CPS, I wasn't aware that I was.  Where might I be able to check and adjust, if needed?  I'm running Win 7, if that is of relevance.

 

And I agree, the space is very tight in the computer case and so I am a little concerned the something might be obstructing fans...I tried my best to not have that be the case but there is very little room at the moment.



#3830 RYSr

RYSr

    Pinball Fan

  • Charter Member
  • 511 posts
  • Location:Mercerville (Central) NJ, USA

  • Flag: United States of America

  • Favorite Pinball: TZ - G&R - MB - CV - Metallica

Posted 31 December 2015 - 12:45 AM

 

Edizzle,

 

Are you boosting the CPS on your CPU or Ram or GPU?

I had this happen when the auto boost setting was pushing the system to far, the fans would speedup and the FPS of the table would start dropping to a stand still.

Under normal desktop it was OK but a demanding game caused it to over clock it.

 

Also if you were in the computer adding ram, make sure a cable didn't move or touch and obstruct the GPU or CPU  Fans.

Rich

Ahh, interesting information RYSr.  thanks for the response.  If you don't mind, you'll have to pardon me as I'm not overly computer savvy.  If I am boosting the CPS, I wasn't aware that I was.  Where might I be able to check and adjust, if needed?  I'm running Win 7, if that is of relevance.

 

And I agree, the space is very tight in the computer case and so I am a little concerned the something might be obstructing fans...I tried my best to not have that be the case but there is very little room at the moment.

 

 

I was more concerned that a wire might be up against the actual fan and stopping it from turning. It wouldn't hurt to open it up and double check. Leave the cover off and look at the cpu and GPU fans and make sure they are turning after bootup.

 

As far as the over clocking, you would of had to load either a mother board utility or a Graphics card utility like  GPU boost to have overclocking happening, If you didn't then that's not it.

 

But it does sound like something is overheating.

Perhaps try taking the new ram out in case it's got a problem, since it's the last think you did before noticing the problem, and see if that helps.

 

If none of that helps you can go to the manufacturer's website of your GTX card and look for a utility download that will show the temperature of the GPU and see if that's overheating.

Rich


Edited by RYSr, 31 December 2015 - 12:50 AM.


#3831 lizard

lizard

    Enthusiast

  • Platinum Supporter
  • 318 posts
  • Location:Australia

  • Flag: Australia

  • Favorite Pinball: Kiss

Posted 31 December 2015 - 02:28 AM

Possibly not related but after installing the vp10 minimal install yesterday i found something similar. While i am running windows 10 not w7 but after the minimal install if i started a table it played fine to begin with then after 2 to 3 minutes the fps would start to drop slowly until it got to 10 to 15 fps and major stutter, and the f11 display would start to flicker to. Even when i just started a table and let it sit there for the 3 minutes it would do the same thing. What solved it for me was in the compatibility tab of the VPX exe it was set to compatibility mode for w7. Clearing the check box fixed it, I don't remember changing it but i could have at some point but it only became a problem after the minimal install. I am running the same CPU and graphics card and 8gig of ram.



#3832 BananaBoat

BananaBoat

    Enthusiast

  • Members
  • PipPipPip
  • 228 posts

  • Flag: Australia

  • Favorite Pinball: Tron LE

Posted 01 January 2016 - 02:55 PM

no matter what i do i cant eliminate the microstutter...so disappointing.



#3833 bent98

bent98

    Pinball Fan

  • Members
  • PipPipPipPip
  • 1,077 posts
  • Location:NY

  • Flag: United States of America

  • Favorite Pinball: Roadshow, Haunted House, Safe Cracker

Posted 01 January 2016 - 03:50 PM

Is there a way to disable Nudge shaker effect in vpx? JP's tables use that and its not good for cabinet mode.



#3834 freneticamnesic

freneticamnesic

    A Faint Ghost Through the Raindrops

  • VIP
  • 3,370 posts
  • Location:Portland, OR

  • Flag: United States of America

  • Favorite Pinball: Star Trek, Black Hole, AFM, Fast Draw, Tron, AMH

  • 360 Gamer Tag: sixgunsounddd

Posted 01 January 2016 - 09:23 PM

Is there a way to disable Nudge shaker effect in vpx? JP's tables use that and its not good for cabinet mode.

 

eNfwDNR.png



#3835 BananaBoat

BananaBoat

    Enthusiast

  • Members
  • PipPipPip
  • 228 posts

  • Flag: Australia

  • Favorite Pinball: Tron LE

Posted 02 January 2016 - 04:18 AM

no matter what i do i cant eliminate the microstutter...so disappointing.

Turns out that while i thought aero mode was ON all this time, it was in fact OFF
Turning it on has magically eliminated about 95%+ of the stutter and overall a much more satisfying experience.

For the devs....is it worth looking into why aero has this impact? Or is this already known?

#3836 fuzzel

fuzzel

    spaghetti code

  • VP Dev Team
  • PipPipPipPipPip
  • 2,818 posts

  • Flag: Germany

  • Favorite Pinball: yes I have

Posted 02 January 2016 - 07:55 AM

That is already known but afaik there is no known fix for this problem. Is your gfx card an older one and doesn't have enough shaders? One reason could be that VPX doesn't have exclusive access to the gfx card (because of VPM) and windows just uses additional gfx card resources even if you don't see the desktop.

#3837 StevOz

StevOz

    Pinball Fan

  • VIP
  • 1,721 posts
  • Location:Nirvana

  • Flag: Australia

  • Favorite Pinball: Scared Stiff



Posted 02 January 2016 - 08:36 AM

I think upgrading to w10 here has solved all those problems, there is no aero and although I only run in DT mode. There is zero stutter at all and that is with 4xAA enabled, a solid 60fps, actually I even overclocked my monitor to 66fps and it still never dropped a frame, this is with a core i3 haswell @ 3.4 Ghz and a GTX660.

 

vpx.jpg


Edited by StevOz, 02 January 2016 - 08:49 AM.

Files I have uploaded here...

 

http://www.vpforums....ownloads&mid=34


logoshort.gif


#3838 BananaBoat

BananaBoat

    Enthusiast

  • Members
  • PipPipPip
  • 228 posts

  • Flag: Australia

  • Favorite Pinball: Tron LE

Posted 02 January 2016 - 09:34 AM

That is already known but afaik there is no known fix for this problem. Is your gfx card an older one and doesn't have enough shaders? One reason could be that VPX doesn't have exclusive access to the gfx card (because of VPM) and windows just uses additional gfx card resources even if you don't see the desktop.

Is this a direct result of the fact VPX is now windowed and not true full screen? If so, is that something which is able to be changed?

#3839 fuzzel

fuzzel

    spaghetti code

  • VP Dev Team
  • PipPipPipPipPip
  • 2,818 posts

  • Flag: Germany

  • Favorite Pinball: yes I have

Posted 02 January 2016 - 10:10 AM

Yes that's the reason. Changing VPX to true full screen is possible and easy to do but there could be some other issues with VPM and db2s. Especially db2s wouldn't work anymore because with true full screen VPX would have exclusive access to the gfx card and other applications couldn't access it anymore. So switching to true full screen would mean to include db2s into VPX.
That's all somewhat possible but it needs some time to implement and I think we are more towards VP11 with such a feature than just a simple bug fix release.
So to keep it short: no it's not possible at the moment ;)

#3840 BananaBoat

BananaBoat

    Enthusiast

  • Members
  • PipPipPip
  • 228 posts

  • Flag: Australia

  • Favorite Pinball: Tron LE

Posted 02 January 2016 - 10:13 AM

Yea that's what I kinda figured. Given where VPX is currently, would a move to dx11 be the next logical progression, or is there more work to be done in vpx?





Also tagged with one or more of these keywords: VP10