Expected result: Instant response to a mouseclick Actual result: Nothing happens for about 10 secunds, then works as normal. Generally I'm very pleased with the software, this is probably the most user friendly and idiot proof program I have ever seen.
My only problem is that it lags A LOT for some reason. I can't go 5 or 10 seconds without having to wait so I can click on something, and I don't know why it's doing it. I have a relatively good PC. It's really frustrating after a while. NET Framework Version is 4. No matter which action i do clicking on a button, whatsoever Vortex stops responding for a while with no application timeout or error message from Windows.
After a minute or more it works again. Any suggestions? Thanks in advance for your help. This is especially annoying with automatic deployment. Switching between 'mods' and 'plugins' is still very slow and becomes unresponsive a split second after switching. This lasts for several seconds up to 10 at times. The unresponsiveness seems to be somewhat dependent on how many entries are on the page.
This problem only occurs moving between 'mods' and 'plugins', and only if the lists are large I have over mods. Switching to any other page like 'settings' or 'knowledge base' in between the two results in a normal load without unresponsiveness.
This works as long as I give the intermediary page a second to fully load. Switching too quickly results in Vortex becoming unresponsive for several seconds. Could you try disabling columns the cog icon in the top right of the tables in mods and plugins to see impacts speeds?
If so, can you narrow down which one? The most likely candidate is "Install Order" and "Dependencies" in the mods list. Further: Could you give an estimate of how many rules you have set up mod order and load order rules?
Vortex Version: 1. Even when not in use it starts to mysteriously consume system resources leading to very sluggish responses, even to watching what i'm typing in this report taking about ten seconds to fully appear.
Sending application state log, hopefully. Hi ChaosGodstone, once you can confirm Vortex slowing down again - can you please help us debug this by:. Biggest impact seems to be from the above. Switching to Plugins tab is pretty slow but could be due to the total plugins. Reenabling the above caused a drop in CPU activity. It would appear that regardless of other considerations, switching to Fallout 4 causes the issue to be made abominably manifest.
At active mods Fallout 4 is quite heavily modded but Skyrim SE is only just behind at I doubt the number of mods per se is relevant, an excessive number of mod and plugin rules is more likely to cause slow downs.
I will add some logging for that with the next release 1. Re: the columns you mentioned: I'm Is it possible that disabling columns in general reduces the cpu activity? This should help us investigate what precisely is going on.
Please let me reinforce that you don't want to record performance stats for too long, that recording can become pretty sizable and the dev tool may even run out of memory and crash eventually.
EDIT: Vortex already logs the time it takes to sort plugins. The sorting times for mods is not logged but on my system even a heavily modded game required less than than a hundred rules that takes less than a second. RE: Columns. Hit a slow down. Not sure if the pictures are any use but I reasoned, what the hell. Ok, a few things: a Deployment is a performance heavy operation, we don't expect Vortex to be buttery smooth while it's doing hundreds of thousands of disk operations in the background.
If this is the only time you notice slowdowns then this is a non-issue. The performance recording too may be causing cpu load on top but that too is single-threaded.
So either you're running something else that is extremely cpu intensive or you have some other software set up that incurs further load, e. Deployment and plugin sorting seems to be the main culprits, but I find it a little strange that Fallout 4 so rapidly does this when Skyrim SE, etc. SSE comes to it in relatively short bursts but it appears to settle down after the fact which Fallout 4 conversely seems to keep untill Vortex is restarted. I will admit I was beginning to suspect performance of equipment was an aggravating factor.
Did another recording where I: Switched game mode, clicked on Mods tab, clicked on Plugins tab and then let it perform an archive check. The only other Windows skinning program active is AeroGlass, which happens to not be fully compatible with the latest Windows 10 update Or just Stardock's program interfering? Ok, so in your new profile Vortex is spending a lot of time parsing the esp files.
To put this into perspective: On my system it takes around 2ms to parse an esp, fluctuating between 0. In your profile it fluctuates between 20 to almost ms, around times slower than mine. Now this is running of a consumer SSD here but even if it's a spinning disk on your system, this seems excessive. Apart from that I can't see anything unusual happening, it's just that everything seems to take excessively long for no apparent reason.
Look at this for example: See that tiny pink bar on the left? That is Vortex updating the ui for the frame in 0. The gray bar at the top? That's the process being blocked for ms doing nothing.
I see how this makes for a choppy experience if the ui doesn't react for a whole second but Vortex doesn't do anything in the time. There is no reason, based on what Vortex is doing, why the process is blocked so long. Windows Defender shouldn't be causing this, I'm running that myself, but especially the performance hit during deployment and the slow esp parsing both point to very very slow disk operations that can't just be explained by slow hardware.
Do you notice that elsewhere? Like, are loading times for games or applications from that disk slow in general? Regarding the Stardock program: It's not like applications communicate with skinning programs, there isn't really anything for us to do to be "compatible".
The only thing I could imagine is that the skinning software achieves certain effects by forcing applications to partially re-render more frequently than usual and that re-rendering in Vortex could be a lot more expensive than in native windows applications. If something external were to force an electron app to draw all the time, that could ruin all the optimization we're doing to achieve good performance.
I could imagine a scenario where - lets say you have an animated background and your skinning software wants to produce a fake transparency effect. It would have to do that by blending the window on top of the background but because the background moves, the window has to be re-rendered completely every single frame, even if the window didn't change at all.
This is purely speculation based on you saying disabling the theme had an effect though. From the profiles you sent it doesn't seem like your Vortex does more work than usual, it just look like that the work takes much more time than usual.
That's all under control of the server. Vortex Version: 0. Best regards, Weston. My internet is fine and I know my firewall isn't interfering with it in any way. Now I can't even do that. Inspect:: mod failed to downlaod due to a time out sorry cant remember the exact wording and i couldnt copy and past from the Inspect pop up info.
I'm getting an odd issue where I have paid for premium download speeds, and get those when I am manually downloading from the nexus server. I've tried letting it through the firewall but I'm unsure of what else could be the problem. I'm unsure if this is a temporary speed issue, as it's only being affected by downloading through vortex and it's been happening since yesterday.
I'm aware that the solution would be to just download manually and install from file, but if there is anything I could try to fix it that would be great. Once again, sorry if this is the wrong form to report this potential bug.
A very painfully slow experience as downloading anything at that speed takes a long time, and I know it's not my internet connection because if I download manually I don't have this problem. Skip to content. Star New issue. Jump to bottom. Labels reference. Copy link. Regards, Helmetmonkey Reported by: Helmetmonkey The text was updated successfully, but these errors were encountered:.
Collaborator Author. Reported by: Zxyphear. Reported by: Agreedious. Reported by: samgibbsn7. Reported by: thmmkr. Reported by: BosDragon. TanninOne added bug and removed bug labels Nov 28, TanninOne closed this Nov 29, Reported by: theblueorphan. Reported by: octavioals. TanninOne added the reference label Mar 29,
0コメント