Jump to content

musp3r

Member
  • Content Count

    3
  • Joined

  • Last visited

  • Medals

Community Reputation

10 Good

About musp3r

  • Rank
    Rookie
  1. musp3r

    [SP/CO8] A 3 - Antistasi Altis.

    Hi Barbolani, I've tried new version, hats off for such a quick resolution of the multiplication bug, for now it work as it's supposed to. Reporting some more info about bugs/typos/writing found on my server/missions ver. 0.20.2. - Assembled static MG saved near the flag disappears after loading previous session http://imgur.com/0OXAYlB. - When saving the persistence in info box you wrote "Disassembled weapons MAY be saved...". Is there a certain condition to save disassembled weapons or more accurately you could write "WILL be saved" if that's what supposed to happen when you put disassembled weapons to the ammo box, as may/will have a different meaning according to native English speakers http://english.stackexchange.com/questions/4919/can-may-will-you-help-me-with-this, which I'm not, but the sentence still confuses me weather the weapons will be saved or I have to do a ritual sacrifice in front of Petros in order to save properly :). - When ordering an artillery strike (mortar team, haven't yet tried other artillery support) You have spelled "Arty" wrong as "Atry" http://imgur.com/E5teGV7. That's of course not a biggie, but this mission is too good to have such typos there, and I believe it's just a simple search/replace correction to make it right. Keep up the good work!
  2. musp3r

    [SP/CO8] A 3 - Antistasi Altis.

    Thanks for the great mission, barbolani. I hope you'll have enough time and interest to get it to stable version. My dedicated server (Antistasi v. 0.20.0 Alpha) also has the asset/units multiplication bug. Steps to reproduce the bug on my server: 1. Connect and pick the slot 2. Get some vehicle parked near the flag 3. Persistent save 4. Abort mission 5. Pick the slot and get back to the game 6. Load persistent save 7. Whatever vehicle parked or garrisoned units get multiplied x2 (after few restarts I can have as many vehicles units that can fit the area, some spawn in the walls etc. and explode.) http://imgur.com/AfxrZBH Usually I start the server with CBA, ACE, ACRE, STHUD mods, so I though to run the vanilla server, start the mission again and see if that could be the culprit. Didn't help, same bug occurs. Same bug occurs if I restart the mission with "#restart". The only things that helps not to experience the bug is to restart the dedicated server, then the persistent save get read correctly with the correct saved number of vehicles/units. I can send the rpt/log if needed to debug. Edit #1. The bug isn't present if I try to reproduce the steps and I've aborted the mission for the first time I've started the server and mission and I save/load the persistent save. Yet on the second abort/load it starts multiplying assets. Edit #2. Tried to set the DS option "persistent = 0;" in the server.cfg, nothing happened, as if the server didn't unload the mission from the rotation after last player disconnected. Edit #3. If I restart the mission with "#missions" and reload the mission from the bank, the bug doesn't occur, at least I have two solutions to get around the multiplication.
  3. I had the same issue, but with ATI 5770, so sorry if it's a wrong thread, but the issue is exactly the same. ArmA2 OA freeze, fade to black screen and then switch to desktop, and stays active, as I can hear the sound and see the task running. It was happening on random times, but very often and it annoyed me very much. I've took a look in event viewer, and saw my ATI driver (atinkvdm or something) has restarted every time i experience that error. At that time I had CIV5, BF2:PR, MOH BlackOps, Massive Effect 2, and some more graphic and system intensive games running without a hitch. My system was ever stable, i could bet on it. Only ArmA 2 OA had issues. And I wanted to play that. So I've replaced drivers, fiddled around with driver, game and system options, reinstalled OS, changed memory modules, power supply, disconnected disks, you name it. I've searched the net for similar problems and on some gaming site (didn't manage to save links) I've read that for some game they had to increase the voltage to the processor, when experiencing same atinkvdm problem. So I've gave it a shot. Usually, I never overclock my hardware. My default q9550 processor voltage in BIOS was 1.2v, and i've increased it to 1.3v. I'm playing ArmA2 OA ever since, not a single problem. I was scared a bit increasing the voltage, but for that measly 0.1v I thought it will not be that stressful to the processor or mainboard. Give it a shot if you want. It worked on my system, maybe it will work for you. * DISCLAIMER * It worked for me and my system. If you damage your system i take no responsibility for that in any way. Cheers, Mus
×