|
#1
|
|||
|
|||
![]()
When I first launch Project 64 (2.3.2.202) and launch a rom, the status bar sits on "Plugin initializing" for a long time and "WMI Provider Host" uses a lot of CPU. When it finishes, the rom launches and the "WMI Provider Host" CPU usage goes away.
I'm on Windows 10 64 bit. Any ideas? Thanks! |
#2
|
|||
|
|||
![]()
I am having the same exact problem as well. Its not game breaking but an inconvenience none the less.
Edit: Windows 10 and 64 bit also Last edited by xnoobsaucex; 9th March 2017 at 01:28 AM. |
#3
|
||||
|
||||
![]()
That's probably caused by the NRage Input plugin.
|
#4
|
||||
|
||||
![]()
Don't know if mine has the WMI thing going nuts,but I also got slow game launching speeds in at least 2.3.0 but even after one point of removing the NRage plugin to try another one at an attempt to test it on Conker,but for whatever reason,Conker just fails to run or crashes,regardless if on default settings or after I tried a tinkered setup that worked in older PJ64 versions.
I really don't understand why Conker crashes in the newer 2.3 versions on Windows. It makes more sense for it to fail on Android but not on Windows. Its not the other input plugin either because another game ran fine with it in use. Game launch speeds were not affected on earlier PJ64 versions with NRage present,so I don't think that is related in this scenario as it usually only makes plugin settings take longer to open. I think I actually remember that it was after a Win10 update when settings starting taking forever to open for me,regardless its still really irritating how much time it wastes over how fast those parts opened before. |
#5
|
||||
|
||||
![]()
Must be a Windows 10 problem with a recent update. Conker's works fine here on latest Project64. And I don't get any delay in plugin initializing. But I'm using Windows 8.1 64 bit.
|
#6
|
|||
|
|||
![]()
I had to launch the game in compatibility mode (Win7) so it would work. Damn Win10!!!
Maybe dev could fix this. (I received my Retrode today. I was upset to see that the emulator wasn't working anymore.) |
#7
|
|||
|
|||
![]()
Sorry for the late response, apparently this forum isn't emailing responses for subscribed threads.
Compatibility mode for Win7 didn't fix the Plugin Initializing delay for me. |
#8
|
|||
|
|||
![]()
Just tested it, yes it is. I tried version 2.3c and that has the problem too.
|
#9
|
||||
|
||||
![]()
this is because of the xinput controller detection.
in a typical game, controllers are enumerated as the process starts, because pj64 lazy loads plugins there will always be a slight wait for each hid device to be checked for the xinput _IG string. There is nothing to be fixed here, as its doing as the code intends.
__________________
Xfire Profile | VBA-M | XBCD 0.2.7
CPU:Intel i7 920 @ 3.8(D0), Mainboard:Asus Rampage II Gene, Memory:12GB Corsair Vengeance 1600 Video:EVGA Geforce GTX 680+ 4GB, Sound:Creative XFI Titanium Fatal1ty Pro, Monitor:BenQ G2400WD HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black Case:NZXT Guardian 921RB, PSU:Corsair 620HX, OS:Windows 7 SP1 Last edited by squall_leonhart; 8th May 2017 at 07:59 AM. |
#10
|
|||
|
|||
![]()
Thanks for the reply Squall. So taking 30 seconds to initialize is expected? I've tried many games that start faster than that and have controllers detected immediately. It seems something is being done differently for PJ64/nrage.
|