stephansabath@t-online.de

I think you dont get it. YOU mixed Steam + Retail. http://dayzmod.com/f...-common-errors/ <---- read me!!! There is something about it.

Did you ever play DayZ right now? So it´s true its not a clean "Steam" install and it´s not a clean "Retail" install and this is the point maybe. You have 2 different BE installs for 2 different Arma versions. Buy OA from steam and i think it will work.

Are you using a NON steam version + a steam version? I´m very sure, that this won´t work!

@Ammo change the graficsmemory ingame to default or something different. Its NOT new, its an Arma2 bug and well known in BI forums. Happens in cities also. Is i said, try to something else and back or so.

It was clearly stated, that sixupdater/launcher isnt implemented till now.

I think that your char isn´t saved correct. Do you play on the same server? Maybe there is an issue with the server saving your char to the DayZ database.

ArmA X owner here. I had to rollback to 1.7.1.5 + beta 93965 to be able to play. I was stuck in "loading" and "waiting for character to create" Are ArmA2 CO (steam) owners still fine?

Hi, Im an ArmaX owner. My char is gone :( i have to start from the coast, choosing my gender before. Are all ArmA X chars wiped/cleaned up now? IGN: TRIPLE playerID: 29058AX

Don´t let us get this thread out of controll again. It was a bit to much before. I feel like a little kid on christmas :)

hmmm I´m more curious ;) Won´t be a bad update for sure. I know what that playerID issue is. I posted a temp solution for it. ;) (ArmA X only!)

Uh... is the playerID issue such a big thing? Did not expect this.

ArmA X chars can´t be fixed atm, but there is a solution. You only have to read this thread. ... BUT this might all be have an ending, when 1.7.2 is out. Good luck with your ArmA X. @Lamkiller You can.

I´m still playing on 93965 patched servers and everything runs fine and smooth.

To see the flashlight right, press "L" as said before and sneak.

High or default

Try to change the "Video Memory" in the options.

Im really disapointed, that ArmA X owners can´t read. Last time! Read the first post. Thats it for me.

:( don´t laugh at me :(

1.7.2 will fix this, so you have to wait, as it was said before.

This is again the "checklist" for all ArmA X owners. Please read it. 1. Do not use SixUpdater! 2. Clean Arma2 X installation 3. update to ArmA2 CO 1.60 official (707MB) 4. update to Arma2 93965 beta * 5. Install DayZ 1.7.1.5 alpha (14 files go here ->.../Arma2/@DayZ/Addons) 6. Start Arma2oa with the beta shortcut 7. go to "Expansions" and check mark "beta", "@DayZ" and "expansions" Play on servers saying DayZ 1.7.1.5 and beta 93965 (use Filter 1. line "93965" in multiplayer) * If you allready installed the latest beta or another, go to.../Arma2/expansions/ and delete the "beta" folder. Install beta patch 93965. Please make this sticky in the anouncement, until this problem is solved with the DayZ 1.7.2 update or delete it. Thank you. Moving my previous post here doesnt make sense! Noone is reading the first post. I wanted this for Arma X owners. But thank you anyway.

Not until you´ve read the 1. post.

you can, be careful, thats all.

Im still here ;) But i wont help .. nananananana :P

? whats wrong with this? This is cleary stated and true, you only got it wrong, mate. This means that "after" 93965 the PlayerID changed for players using ArmaX and since then, all ArmaX owners have this problem with the following beta patches. That was made, because sometimes a normal Arma2 CO owner and an ArmA X owner had the same ID. To prevent the "key is allready in use" they made the "XY" or somewhat behind the normal ID of ArmaX players, i think. Thats the only reason that makes sense.

It was never said, that 94444 fixed this! @PK Richie Thank you very much :) I allways try to help and I know what it means to make a mod and that it takes time to find out, what went wrong. Regards