PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Low Framerate in POB
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Lua
- Sterne
- 5.4k
- Forks
- 2.4k
- Ø Merge
- 1 T. 12 Std.
- Gemergte PRs (30 T.)
- 26
Beschreibung
Check version
- I'm running the latest version of Path of Building and I've verified this by checking the changelog
Check for duplicates
- I've checked for duplicate issues by using the search function of the issue tracker
What is the expected behaviour/value?
Windows 10 x64 latest, 21h2
Drivers latest
CPU: Xeon 2670v3
GPU: AMD RX 570
RAM: 16GB DDR4 2133mhz
When launched in any mode (with compatibility and / or with full screen optimization disabled), pob shows through rivatuner 20-25 fps, but its only affects only Tree tab. Its very uncomfortable. In Skills, configs /etc i have at least 60 fps. The bug appears in both of POBS (fork too)
This problem appeared after I moved from nvidia 460 gtx to r9 270x. After that, I completely updated the configuration for xeon and rx 570, but nothing has changed.
Full package vcc++ 05-21 x86 and x64, net framework 2.0, 3.0, 3.5, 4.0 have been installed. Directx 9-12 too.
I don’t know what to do anymore, it would seem that I tried everything that could at least somehow influence. My friend has an almost similar setup (2640v3 + rx 470) and everything is fine with him in this regard, we have the same windows. Tell me where to dig :(
(build paste just null build)
What is the actual behaviour/value?
Low Framerate in POB at high pc
How to reproduce the issue
Launch POB -> enjoy 20 fps
Build code
eNqtWltz2jgUfk5_hcfvCeGapEPaIQlJmIGUjWm7-9RRzAHUyJbHkiH01--RbII3hXCsbh6oMd-5H52Lpt3PL5HwlpAqLuNLv35y6nsQh3LK4_ml_3Vye3zuf_70oTtmevFldpVxYX759OGoa589AUsQSOd7mqVz0N82nJo_kFPCYr0AGY_YT5neyeml_yBj8L0nFk-53nwLBVPqgUVw6QchEvseUyHE0-vt-xwYMR4HMnwGfZfKLLFilxxWIzlFzGA0_vI4KQnlcVko6nzUHQu2hjTQTHsKPy79HprO5nDDIvxEbkxkYNxwft4-q7ca9rPp13YTBwnAtETU2Accp9CfzSDUfAnXKdfXCxaHW3Gn--iqYkeZ0DwRHNKSVu19FPe_Mb-42IedSM3EzTh4hTZOGp3G1knv00l9WP_vXC-uBDrUQYqhHcxjrsGReCy5kvEf2Fcm3R-iTAg8PTSsjJ547OSNEYvZtVQEnw_5DGjIfkDDPeIxoiGNlmNI8aBrurKVCAoJAYQSi0kVGVVISna4CXOg7AcuBA6CAr2tJI29qBt4IaAGsSbxWkptm8Ah3ezR69-PX5Gds5Nmp3Vx0bmon55edPbaZO3H7sAjJkbshUdZhKVwwp5hK7V5tr9umrhthZ6-0x3CjwY7iENaMnyNU1CQLktNpUMkKMK7Lfun7xI-whximlJDgHBxh533kWmgHYdXVPt95xgsyTkGuMM5bSJBBecYwjfOObl4D1zRPd9ZOiUc1xjS-TpYcBAEtPVlmYTk0zIBMR3KJBXt7i-ZKp_qeud9a3I4LTkApwYkmAJ1VBqn8qcZxkQ1sl4aySwlxiMHkwwYL9aKhzhG2CH0EaZZSKuArzPlSC4hwgy3AylOw1s37yO9EjhHUw1HtkJUouhpzcLnGzmdQyUh1SmCLEnwnJtsodLd8hS9rHipAR53COgvuCtcs4Qyu5kjRRWwRZMFDPl8oWMcJelS3pDQbVkwqSoYs4WTRdziWEyaicdyhSwXZtFU1dDY5retfa8eKcS_1mT-_4GTBPTjaZaaHCXLeEvxu5huzS7i5mkQJTLV9uU1E6GyLAdxkmkvtlt0xFX44ymbzczC7KOI1G75_dvb_vVk8K1faFEmUc9ciB9xFj2ZnTL_d1tWArCVygulECxRgLt2zIXvcXwIDGWAtTnUBDQOYMUOfhiLPTRMObrvMNRsngRV7R5_GGdWbAIM48AEUF00WSdgIq5oXiqK3GGs3aUJuHz1pZhlF2yK0yFkawLudYQgYPsCelyYHkfx0wgTPW-OFDQ2q5Q_ZZqUUXb4J2hgxmCCWeVBj5T5FFgxqBDEF1PZYWTRAShph2MCMUQ3MANMZtJBtsUh39HysrcpcV17ipSnsPbdQaSu1thLbo1D31yiRExjukE0NFeWE2kqKgs1pMP8CnPGhDJFsczm0tdphi-nMGOZMO__ypjgel1otn1fMLFv1UKuzFiSczLnW2FMhsP8l57QBRMjZiPX2jRJATxmJzozQ5o6mzsGv5TvRAdT0zLQIIXqr4tEv_SxPmNdx4f2-Xmz6Xsa2ZXuY-tnxVVrTm44H3X7UzzT0wdDV8vffH0c2oejhdaJ-lirrVark4TphZzBC47MJ6GMagmyQS2PbXs4NoJqPfy7mvfsn2VU23Dq5ne2uYBuzVhjI2jMNQ8PEo-e-c283HyxzvjGYeUpwHq_CHRqLPwlZfTPpd9o1XNv3gPTI5YUnje_FpFoFnHAynrD0UOpzbRNQA3wbxxkGmd56-0ONAaj8L15DkDb6-VMQX5f8B1YImP72ojKG2UO3AuymVsvPB0IuWmqOcyrByuWeL2ntVJMeLmTvDZSIds8RrW9pG_JGjSy91FXUmrlqNAuWw4odQVCVyS5xfx99poklRq7VGq6uZfmhMb_RNZyU7LjJq3j7k2XfDoQgXvALq-rCtqRSR0XOQfS707goq1cGDfdT1HdRV7LLRfqbpnXOhweimOrst2VXo6Gk-pO20EfhxrYPCRmuvbyEa9i-HZ72Sm_2i5EpCNJCYSTnW1ntzYc4t5xO0lNt_RtVs-ylnvZd8jpurPzm5SEaFFADmr_wfBDjKR7FDoOWekehj9IF2pJNrTEU0OHOnjukcdz2iRQuVDsda9juaDH08WcJsFPdfcwtJy91XaxhnJe3JP8gEq9KBM7elu3VuyQdiG2S6i9vpXxjM8R0a29_Y9X_wK6tsEG
Screenshots



Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne damit, POB zu starten und den Tree-Tab mit Skills und Configs zu vergleichen, wobei der Bericht angibt, dass die framerate normal ist. Reproduziere das Verhalten mit 20–25 FPS auf der aufgeführten Windows- und AMD-Hardware und verwende den bereitgestellten Build-Code und die Screenshots als Kontext. Als erledigt gilt es, wenn der Tree-Tab unter denselben Bedingungen nicht mehr die gemeldete niedrige framerate zeigt.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- lua
- Bereich
- desktop-dev, performance
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100