I've updated to MeGUI 2525 and DGIndex latest version. At random DGDecodeNV when creating the index file, it will take an infinite amount of time to create the index file as the time remaining keeps going up instead of down. Job 30 (Main Event June 06) was taking 52+ minutes to create a DGI file. Logfile is attached.
I do NOT get this problem when manually creating an index file without DGDecodeNV (when not using MeGUI).
There is not much what I can do. You can try to execute the command line without MeGUI (it is written in the log). When this also fails/stop then you can get in contact with the author of the tool. If it only fails when using MeGUI please have a look at the task manager if the process is still there or not.
But before you do these things you should update first to the latest development build as the newest DGIndexNV version just got updated today which may fix this problem.
Happened again today. What should I be looking for in Task Manager?
Sorry, I did not see your reponse before. The process you need to find is "dgindexnv.exe".
Also please update your DGIndexNV/MeGUI version.
My original post said "I do NOT get this problem when manually creating an index file without DGDecodeNV (when not using MeGUI)."
Bold word should have said WITH. Can you correct that please.
By the way I was talking about DGIndexNV in my 1st post. Said DGDecodeNV by accident.
What does executing the command line without MeGUI do?
What does executing the command line WITH MeGUI do?
How do I execute the command line?
Observe in both cases if at the end the dgindexnv process is still there. If yes and it happens only in 2 then I have to investigate. If it is happening in both cases it is something the author of the tool has to investigate.
In ANY case update before to the latest MeGUI and DGIndexNV build!
Last edit: Zathor 2015-09-17
Can you please give me a step by step instructions of what I'm supposed to do as this is confusing.
So when I notice that the index is taking an infinite amount of time to be created what do I do then? Do I just leave that index running or do I abort it?
I left it running then I looked at Task Manager processes. DGIndexNV was there. It showed CPU: 0%. With DGIndexNV still running I then ran the command line like you said. It says this: C:\Users\Dave\Project then it had a number that went from 1 to 100. It reached 100 then I didn't see any further activity in CMD. I assume that means the index file was created successfully? Also I saw a new DGIndexNV process and it had around 20% CPU usage.
You said "Observe in both cases if at the end the dgindexnv process is still there. If yes and it happens only in 2 then I have to investigate". What do you mean by "2"?
I assume the command I ran used MeGUI? How do I run the command without MeGUI?
As you have written in the DGIndexNV thread your problem is solved. Is that correct? Then I will close this bug report.
No it's not solved. I thought upgrading DGIndexNV solved the problem as I never had the problem for several days but I got the problem again. As per my last past here I'm waiting on an answer from you.
Can you please give me a step by step instructions of what I'm supposed to do as this is confusing.
So when I notice that the index is taking an infinite amount of time to be created what do I do then? Do I just leave that index running or do I abort it?
I left it running then I looked at Task Manager processes. DGIndexNV was there. It showed CPU: 0%. With DGIndexNV still running I then ran the command line like you said. It says this: C:\Users\Dave\Project then it had a number that went from 1 to 100. It reached 100 then I didn't see any further activity in CMD. I assume that means the index file was created successfully? Also I saw a new DGIndexNV process and it had around 20% CPU usage.
You said "Observe in both cases if at the end the dgindexnv process is still there. If yes and it happens only in 2 then I have to investigate". What do you mean by "2"?
I assume the command I ran used MeGUI? How do I run the command without MeGUI?
This ticket can be closed, correct?
Yes close it. I will open another ticket.