Closed GoogleCodeExporter closed 8 years ago
Is there any way to reproduce this issue?
Original comment by ShadowIs...@gmail.com
on 2 Feb 2012 at 2:22
Hm, I guess by running an application in a read-only folder.
Original comment by normen667
on 2 Feb 2012 at 4:55
@Normen: When the application runs in a read-only folder, the <user>/.jme3
folder is used. What I am asking is, under what circumstances can the natives
fail to be replaced in that folder?
Original comment by ShadowIs...@gmail.com
on 2 Feb 2012 at 5:58
Yes, and the failure only happens when that is the case, from then on I don't
know, I do not own a messed up windows.
Original comment by normen667
on 2 Feb 2012 at 9:15
I am marking this issue as fixed since I have not heard of any reports of it
recently. I believe it might have happened when a new version of jME3 ran on a
PC where an old version was run on.
Original comment by ShadowIs...@gmail.com
on 29 May 2012 at 1:19
Original issue reported on code.google.com by
ShadowIs...@gmail.com
on 13 Jan 2012 at 5:11