ryteklikd

Update: Sorted this out, not a DayZ SA problem at all. Admin may remove this thread or keep it around if it's going to help someone in the future. So a week or so ago I initially moved DayZ SA from my HDD to SSD for faster loads (before I got Arma). I had to run Steam as admin to get the validation to work because my Windows 8 has that crazy C:\ locked business going on - and my PC wasn't restarted until I had this error. When I restarted I didn't load Steam as admin and thats why nothing was working. Simple fix, logged out of Steam, restarted it as admin, launched DayZ SA. *sigh* Sorry to waste your time.

Hi there First time DayZ forum poster here, I apologise if this isn't in the right section of these forums. Let's get to it; prieveously I had DayZ SA installed, running, and didn't encounter any in-game error preventing me from playing. Steam logged over 100 hours. A friend of mine wanted me to try the DayZ mod on Arma 2 with him so I purchased and installed Arma 2 + OP expansion, ran them, installed DayZ Commander and patched Arma 2 to beta and installed DayZ Epoch. Started up the DayZ mod and viola, no problems. However, 10 minutes after launching Arma 2 DayZ mod, I went back to launch DayZ SA from the icon on the desktop (it's purchased through Steam). It indicates its loading, then stops. Nothing gets launched. I dont even get to the splash screen. Checked in task manager and cannot seem to see anything DayZ related. I've also tried launching through Steam via library, same thing. Multiple restarts, nothing. Validated game files, nothing. Googled this problem and can't seem to find anything. Now I know most of you will probably get me to uninstall and do a clean reinstall which means I have to redownload. If I cannot find a work-around I will, but for now i'm trying to avoid that 2-3gb download. So info, I have two steam directories. One in C: which is an SSD where DayZ SA is installed (and was working) and one in E: which is a HDD where Arma 2 + OP + DayZ mod was installed. (So they're on separate drives) Now what I think is the issue if any of you are familiar with DayZ Commander, are those settings (which I followed a tutorial and enabled/ticked these): "Launch using Steam" "Replace original Arma2OA files with beta so Steam works" I went back and disabled these, restarted and tried to launch DayZ SA - still nothing. Unsure what I did along the way to mess up SA but here's me thinking its on a separate drive, it'll be fine - if there's any conflict at all? Hence thinking DayZ Commander has screwed something up. Anyone have a fair idea what's going on here? Anyone have both DayZ SA and the mod installed with DayZ Commander and it's all working? Any idea's? Help would be greatly appreciated, thanks in advance.