Jump to content

Spartan190

Member
  • Content Count

    9
  • Joined

  • Last visited

  • Medals

Community Reputation

1 Neutral

About Spartan190

  • Rank
    Private
  1. Thanks for adding the command-line support. Works perfectly. Was now able to create a repo. Will try it for my ppl :)
  2. Spartan190

    Enemy occupation system (eos)

    That's normal, the value for visible/invsible is just for seeing if enemies are in the zone or not. You need to set a invisble marker to make the marker completely invisible.
  3. Just the standard features for building and updating the repository, that my clanm8s can connect to the server and synchronize on their windows client. So that we can add/remove Mods and they just need to synchronize with the server and they are always up to date. Also like the ACRE installation wizard. That way we don't need to explain every step for ACRE.
  4. This tools looks great. Will there be a linux command-line/terminal version? I would like to use the sync feature in my clan but only have SSH access to the server (don't want to install a gui just for that). Or that I can create a repo remotely via my client.
  5. Spartan190

    Enemy occupation system (eos)

    I used it in my Testmission and had no problems with it. Also nice that you now did add the getMarkerSize function and a SafeZone var. Works really nice just need to find out which Safezone size fits best for me :) Great work keep going on :)
  6. Spartan190

    Enemy occupation system (eos)

    it can be found in the eos_launch.sqf right under the variable initialization.
  7. Spartan190

    Enemy occupation system (eos)

    Looking forward for it. Implemented it for myself for testing etc. Function can be found here
  8. Spartan190

    Enemy occupation system (eos)

    Hi there really nice script just tested a little around but need to get more into it. I had one thing that annoyed me. It was the static Markersize for testing and spawning. I thought: easiest way would be if the size of the Marker defines the size for checking and spawning of the AI. I have a little change you could make: Instead to set a static Markersize you could get it from the Markers. I tried it out and works like a charm :) So the size of a marker defines the size of the area for the Units. You just need to replace _esoMarkerSize in eos_init to getMarkerSize _x select 0 in every foreach loop. Then the size is defined by the A axis of the marker. Also possible to change that A and B axis are used but an extra parameter is needed.
  9. I also got problems with my FPS. Got a nVidia Graphics Card (GTX 560Ti) and AMD Phenom II X6 1090T Single Player no problem everything works smooth on high. Multiplayer depends on server on some no problem but mostly about 10-15 FPS CPU only 30%-50% used (all cores). Changing graphics settings makes no difference, still running bad.
×