Open ggml opened 7 years ago
joreg not sure if it would solve the 5min delay but the idea is that a pack would contain a nodelist.xml so that vvvv does not have to parse the directory but can simply rely on the info in the nodelist.xml and typically this reduces startup-time.
@vux is there a reason you're not adding one for the dx11 pack? here is how: https://vvvv.org/documentation/nodelist-(vvvv)
Yeah one liners will tend to get closed. Does not start is just way too vague and reasonably pointless, sorry...
So now there's a bit of details
Thanks
Quick glance at the log suggests it's looking 5 minutes for a 0.v4p. Possibly you have some junctions/hardlinks/symbolic links to big/remote drives or those of non-native filesystems that need ages to scan for 0.v4p? (Just a guess, becaue i'm tampering with ext2fs and hardlink shell extension a lot, both of wich are damn useful but also damn tricky sometimes.)
@blausand No, it's coming from the [13:44:16.465] scanning for Externals
But well considering the absence of information there's not much I can do there to be honest, only thing I know from several users is that b35 is generally slower to boot (plus using at least double the memory just from opening)
sorry for late,
tried this:
none worked with dx11 pack folder inside, all worked without it
all logstartups say "exception occurred while trying to create an instance of type 'VVVV.DX11.Factories.DX11NodesFactory'."
screenshot of defender setup while still freezing
any idear what software might interfere in this case ?
Hey @ggml saw your post over at the forum.
Just a stab in the dark, before you start wiping installs: what other packs do you have installed?
@velcrome only dx11
I encountered the same issue, and after a bit of debugging, solved it by installing the SlimDX runtime, found on this page under ".NET 4.0 / x64":
https://www.slimdx.org/download.php
Now it works. Otherwise it would freeze on the vvvv splashscreen, exactly the same bug report as ggml's. Nearly fresh install of Win10 with updated drivers, fresh install of vvvv that works fine without dx11 pack, tried multiple versions of everything. I ended up building dx11-vvvv from source and running it in the debugger to narrow down the problem, which led me into SlimDX. Clearly those runtimes weren't originally required, but perhaps they include some other directX stuff that I didn't have. Or not. In any case, @ggml if you're still onto this, you could try that and tell us if it helps.
deleting report 294 for documentational reasons didnt make the issue go away, so here it is again.
added the 1.0.1 x64 pack to a clean install of beta5 and v4 wont start anymore. (remove the pack and it works again)
regarding more details: (please ask what you need so i dont have to reopen a third thread)
he produced this log: