My computer simply refuses to install it. It's a pretty new machine, just a few weeks old, Win 8.1, I've run as admin, changed compatibility settings several times, turned off DEP, turned off "read-only" property of the Reloaded folder, blah blah blah. I've even tried to delete it in order to download it again and the computer won't even let me do that. It claims it's open by itself! Tried shutting of the antivirus but it doesn't even know it's there. Does anybody have any suggestions? I'll try again to download it into another directory, of course, but this kind of behavior by any executable kinda scares me!!!!





EDIT: I've downloaded it again, and get the same response. It doesn't show up in task manager so I can't even kill it, yet still calims to be open (in itself) even immediately after a reboot. Scary. Weird.





EDIT #2: Figured it out, unknown process running (I believe it is from NVidia); stopped it from running on startup, rebooted, all is fine; process is Nvtmru in case that helps anybody!





Just a note-I had updated my video card drivers within a hour prior to downloading and installing...the driver is still in beta.

I've been able to install it fine but now FPSCR is refusing to load up the default green grass field. The editing screen stays black and the engine freezes on me. I can access the legacy pack in the entities tab but if i try to select anything the engine just packs in.



My computer is new-ish, its a laptop with an i5 processor and 8 gigs of RAM so it shouldn't really be having performance issues.

Hmm. They installed just fine for me. My install is not on c drive but a different one. I have put about 30 or so in a test level. They run in test game mode. Some texture lettering is reversed on Industrial (27) and industrial (16), But there is a lot of stuff now.

I did the download from the store on some packs and the editor locked a couple of times at the end of the download. Reload would not run. I did a restart on my PC and all worked fine. Windows 8 GE Force GTX 650

@tommy8 : May be related to the other issue you reported about your version failing to work fully and consistently. See other thread.