ติดตั้ง Steam
เข้าสู่ระบบ
|
ภาษา
简体中文 (จีนตัวย่อ)
繁體中文 (จีนตัวเต็ม)
日本語 (ญี่ปุ่น)
한국어 (เกาหลี)
български (บัลแกเรีย)
Čeština (เช็ก)
Dansk (เดนมาร์ก)
Deutsch (เยอรมัน)
English (อังกฤษ)
Español - España (สเปน)
Español - Latinoamérica (สเปน - ลาตินอเมริกา)
Ελληνικά (กรีก)
Français (ฝรั่งเศส)
Italiano (อิตาลี)
Bahasa Indonesia (อินโดนีเซีย)
Magyar (ฮังการี)
Nederlands (ดัตช์)
Norsk (นอร์เวย์)
Polski (โปแลนด์)
Português (โปรตุเกส - โปรตุเกส)
Português - Brasil (โปรตุเกส - บราซิล)
Română (โรมาเนีย)
Русский (รัสเซีย)
Suomi (ฟินแลนด์)
Svenska (สวีเดน)
Türkçe (ตุรกี)
Tiếng Việt (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
No difference in views 1w, 3, 6, still framedrops from 60 to 45-48 (=stuttering) on MB trial table.
/added observation for extra info: View 1w with vsync off: 55fps (vs vsync on: 45-48fps)
View 7: 54 fps when the camera is on the upper area, 45 with FX visuals OFF!?
Views 1, 2, 4, 5, 8 are ΟΚ, locked 60fps.
All other tables Vol1-4 & Creatures trial table: no framedrops in every view.
Testbed: i7-7700HQ, 8GB RAM, GTX1050 2GB (dedicated) Drivers 441.08, W10 Home 64-bit v.1903 (build 18362.449) on a SSD.
in-game settings: 1920x1080 fullscreen, Vsync ON, reflections ON, 8xMSAA, Shadow Quality: High
nvidia additional settings: 8xAF, AA-mode: enhance, 8xAA, 8x (supersample) AA-transparency, Texture filtering - Anisotropic sample optimization: Off, Texture filtering - Negative LOD Bias: Clamp
Perhaps Monster Bash is a little more intensive and breaking V-Sync (60Hz/fps) but I honestly think 4x MSAA is realistic for that GPU.
this is a test setup (see: testbed) meant to stress things to show bottlenecks and performance problems and where they occure, 8xMSAA is sufficient anyway. But that is not the problem nor is how a GTX1050 performs and which settings one should use, the problem is with that extreme setup only particular views of MB show stuttering problems while the others who don't differ that much like 4 (ok) to 3 (not ok), 1,2 (ok) to 1w (not ok) don't.
View 2 and 8 seem to have improved and running stable at 144fps, until multiball where i'm still getting drops. Every other view still running in the 70-85fps range at all times.
I found dropping AA from 8x to 4x significantly increased overall performance and pretty much fixed the issue for me. Never had this problem on any other table so is there a problem or is monster bash really that much more demanding? I don't know.
Bug confirmed by other users here and on discord.
MB is much better with msaa 0ff. laggy with msaa 4x and 8x. View 7 and 8 are not so well. Multiball has a bit lag too.
Cftbl works well with shadow low.
i5 6500T @ 3.1GHz
8GB DDR4 @ 2133MHz
GTX 1060 6GB
Windows 10 64bit
32" 144Hz Freesync (g-sync active) playfield
22" 60Hz backglass (will soon be replaced by 24" 144Hz)
I use NvidiaInspector to limit the frames @ 120fps
Game settings:
1440x2560 (cabinet mode)
Fullscreen
Ball trails ON
Shadows HIGH
V-sync OFF
Reflections ON
4xMSAA
Views 1,1w and 2 are used.
I run PFX3 on 120fps (playfield is set on 120Hz).
MB tables did play @ 70-85fps before the beta.
With the beta it runs @ 85-100fps. So there's improvement!
Compared to the AFM table, MB runs just a little worse. (AFM runs @ 95-110fps)
MB now runs just as smooth as any other table using v-sync on 60Hz TV.
Ball trails on
2xMSAA
Shadows High
and animations on, no problem.
So GREAT work ZenStudios.... please add this to your main release branch.
Thanks for all your feedback on this topic.
During the weekend, finish any game you have in progress, as there's going to be an update coming out on Monday, that'll make you lose any saved game on the table.
Thank you for your patience!
This is on an RX580 @ 4k with no AA. But now I can turn AA back on and still hold 60fps to match my TV.
Thanks for reporting the issue!