Search titles only
By:
Home
Forums
New posts
Search forums
Articles
New articles
New comments
Search articles
Pinball DB
Pinball Tables
Pinball Games
What's new
New posts
New articles
New profile posts
New article comments
Latest activity
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Welcome Back to Digital Pinball Fans -
please read this first
For latest updates, follow Digital Pinball Fans on
Facebook
and
Twitter
Home
Forums
Digital Pinball Games
Digital Pinball Cabinets
Arcooda Cab Views 2 to 4 play in Slow Motion. View 1 fine - Build 1.70.18 (5th June)
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="gust334" data-source="post: 274448" data-attributes="member: 7347"><p>I think the most useful bit of data is observing the CPU and GPU activity, reported by Windows Task Manager, as the camera views change. If accurate, it is showing that neither one of them is working very hard at all. (I am using an i7 laptop with a 980M GPU.) When the slow camera views are selected, the GPU is in the sub-5% range, and when the fast camera is selected it jumps up to ~23%.</p><p></p><p>On this basis, I would expect that raw performance available from the system should be sufficient for the game.</p><p></p><p>Games that really stress the system show much higher GPU and CPU activity, and the system cooling fans have to turn on. If I have a really big city loaded in Cities:Skylines, or am playing a shooter with a lot of smoke or water, then the fans go on. The fans have never turned on when I am playing Pinball Arcade.</p><p></p><p>One observation I did make is that in the three slow camera views, the main CPU utilization is unexpectedly high, ~25%. Windows Task Manager shows that McAffee VirusScan is loading the CPU up. In the fast camera view, McAffee has almost no activity. This might point to some optimization in the code that looks suspicious to AV software, or the slow views are using some shared Windows resources that McAffee also needs.</p><p></p><p>I did try disabling McAffee, and that improved the slow cameras from 6-10fps to the mid 40's, but the GPU utilization is still very low.</p><p></p><p>Unfortunately, I do not have any experience as a DX11 developer, so it is near impossible to guess what might be the problem. But based on my experience with embedded real-time systems, I would think some sort of handshake between threads is happening out of order or timing out. I wonder if the software is dependent on some Windows resource or component for communications between threads... the issue could be outside the Farsight code.</p><p></p><p>Hoping to get more suggestions from Farsight sometime soon.</p></blockquote><p></p>
[QUOTE="gust334, post: 274448, member: 7347"] I think the most useful bit of data is observing the CPU and GPU activity, reported by Windows Task Manager, as the camera views change. If accurate, it is showing that neither one of them is working very hard at all. (I am using an i7 laptop with a 980M GPU.) When the slow camera views are selected, the GPU is in the sub-5% range, and when the fast camera is selected it jumps up to ~23%. On this basis, I would expect that raw performance available from the system should be sufficient for the game. Games that really stress the system show much higher GPU and CPU activity, and the system cooling fans have to turn on. If I have a really big city loaded in Cities:Skylines, or am playing a shooter with a lot of smoke or water, then the fans go on. The fans have never turned on when I am playing Pinball Arcade. One observation I did make is that in the three slow camera views, the main CPU utilization is unexpectedly high, ~25%. Windows Task Manager shows that McAffee VirusScan is loading the CPU up. In the fast camera view, McAffee has almost no activity. This might point to some optimization in the code that looks suspicious to AV software, or the slow views are using some shared Windows resources that McAffee also needs. I did try disabling McAffee, and that improved the slow cameras from 6-10fps to the mid 40's, but the GPU utilization is still very low. Unfortunately, I do not have any experience as a DX11 developer, so it is near impossible to guess what might be the problem. But based on my experience with embedded real-time systems, I would think some sort of handshake between threads is happening out of order or timing out. I wonder if the software is dependent on some Windows resource or component for communications between threads... the issue could be outside the Farsight code. Hoping to get more suggestions from Farsight sometime soon. [/QUOTE]
Verification
Post reply
Members online
No members online now.
Latest posts
D
Anyone still playing?
Latest: Dan
Mar 3, 2025
The Pinball Arcade / Farsight Studios
Home
Forums
Digital Pinball Games
Digital Pinball Cabinets
Arcooda Cab Views 2 to 4 play in Slow Motion. View 1 fine - Build 1.70.18 (5th June)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top
