Jump to content

skruis

Member
  • Content Count

    433
  • Joined

  • Last visited

  • Medals

Community Reputation

180 Excellent

3 Followers

About skruis

  • Rank
    Gunnery Sergeant

Profile Information

  • Gender
    Not Telling

Contact Methods

  • Youtube
    https://www.youtube.com/channel/UCarjaGBJG3F2kU8Ll4CWJIQ
  • Steam url id
    skruis

Recent Profile Visitors

2233 profile views
  1. I've released the mod as part of an open beta to the workshop. You can subscribe there to get the updates: https://steamcommunity.com/sharedfiles/filedetails/?id=2902761497. Should make testing much easier. This does not include the 'side' visibility updates. I'll release that soon. Oh, also, it will, by default, open a browser window now automatically. I added this for new users. You can edit the settings file to disable it.
  2. Well, see now it gets complicated. So lets say i track your side prior to death: revive systems jank that up because some of them prevent death, right? Lets say i track it at mission start, mission designers might add some janky starts where you spawn as a civ and then have your side change or something. I could go based on faction but what traitor missions. I could check last side when health was above a certain amount but thats not foolproof either. Im open to suggestions.
  3. Ill look into that. The script is grabbing the ‘side’ every few seconds so Im guessing thats how the setCaptive works behind the scenes. re: touchability: good feedback. Ill increase the size and spacing.
  4. Another status update: got a little sidetracked when I realized just how much memory the map exports and transfers were taking up. Running Altis on my pc took around 4.5GB of RAM but exporting it caused Arma to sky rocket to just about 10GB. This is a combination of storing all of the exported information in memory while serializing it to JSON in memory before writing it all to disk. I've basically broken up the serialization into smaller pieces. There are still optimizations that can be made but I've reduced the impact to a rise of around 6GB. Unfortunately, to accomplish this, I broke up the world data breaking it out from a single json file however that will also make world exports easier to debug in the future anyways...the json files are now mostly human readable. The worlds are now exported to folder per world with a world file and a series of chunk files, all json. I tried a few different methods but this was the right balance of impact vs ease and it plays nicely with the web app with little memory impact there so, this is what I'm moving forward with for the time being.
  5. Just wanted to provide a bit of a status update. I'm in the middle of yanking the web app out of the bundled web server and will host it centrally. It will make deploying updates easier and make it easier for testers. After the next release, you'll only need to update if the @athenamod or its contents change and I might even just post it to workshop to make it even easier for you. Speaking of which, the web app should notify you and include a link to the latest version of the @athenamod when an update is released which also reminds me: I've also included an interface with version history/release notes. I should probably add links to the Workshop and this forum thread. Other than that, the code base has gotten large and wild enough that a refactor was due so I'm going through it and cleaning it up. It's gotten to the point where things work, now I need to make them maintainable. Additionally, because the app is able to be opened without Arma running, it made sense to add the ability to load a world without being in a mission however you'll only be able to load worlds that already in your cache. I will not be providing world downloads myself but when the community server is released, much farther into the future, that will include the ability to share worlds. As far as things I've fixed: 1. I've resolved issues with the group markers not changing correctly when existing/entering vehicles. 2. I've corrected issues with the waypoint markers not being removed correctly. 3. I've improved the group leader change mechanics so that the new group leader has the marker shown. 4. I've changed the tags mode to player + group leaders and enabled it by default. 5. I've resolved issues with sprite scaling for respawned units 6. I've resolved issued with tags not appearing for respawned units. So work is still progressing. I keep going back and forth about the hassle of storing the libraries (locations, vehicles, weapons) client side. Its extra work but it'll make things easier. I'll rework that process ... again and I'll release the update after. Oh, also, there will be another small change: a patreon link will be included in the app. Totally optional.
  6. Played a little arma last night, found a few bugs: 1. Icons for respawned units are not created at correct scale 2. Group icons are not reverting back to infantry after exiting vehicles I'll try to have these fixed today. There might be some merit to storing a copy of the app on a central website so that people who are beta testing dont have to constantly reload the wwwroot folder. I'll look into it.
  7. Hmm, ok. I was able to join a mission in progress as well but I had problems starting one. I'm testing on a new server I put up so I wasn't sure if it was the server or me. I'll investigate a bit further. Thanks!
  8. @Tankbuster Have you run into issues using it in multiplayer? I can't seem to start a mission with it enabled.
  9. If it's one of those 8" tablets, they tend to be lower spec. I bought a couple of 8" Windows tablets to test out at a few clients and they worked but barely. Anything beyond browsing the web was just too much for them so I'm not surprised they couldn't run Athena. You shouldn't have needed to dump the worlds for the version you were using but for this release, you'll have to. Speaking of which: AthenaWeb_Alpha_20221120.zip 1. Adds support for terrain location types: icon, name. 2. Second attempt at an interface for assigning icons/textures to units and groups based on the vehicles they occupy and weapons they carry. 3. Deleting multiple worlds via the interface in the web app now also deletes the chunks for the world 4. Misc little fixes Sorry for the delay in getting this update out. You'll need to delete the worlds (both in the app and in the <appdata\roaming\athena folder) and copy the included Library folder to your <appdata\roaming\athena folder.
  10. Locations Image Revised Vehicle Classes Management Revised Weapon Classes Management Library Files / Location To start with, I've added support for drawing the 'name' and 'icon' type map locations as seen in the Locations image posted above. They counter scroll meaning their size stays the same as you zoom in/out. The font is Roboto Condensed? which is what Arma appears to be using. It's a google font so I've added a reference to the google font to the app. Additionally, most location icons have been added as well. There's a few I'm missing like side_AA (substituted side_unknown for now) and respawn_unknown (substituted respawn_inf for now). I must not have exported those graphics years back when I originally tried to implement them. The locations that are currently shown are terrain locations, not scripted. I'm not currently collecting locations created during the mission. I plan to add that support eventually, probably when I get to markers because the two are so closely related. I had to make changes to the formats of the locations which does affect the worlds. Because of this, you'll have to delete the worlds from the <UserProfile>\AppData\Roaming\Athena\Worlds folder and you'll have to remove them from the cache in the web app. Sorry. I've revised the vehicle and weapon management screens. I wasn't a fan of the UI and the multistep process. For vehicles, you select the category. This is based on the Editor Sub Category in Eden. When you select a category, the vehicles belonging to that category are displayed in the vehicle list. You can apply the textures to the category, as defaults for all vehicles in that category, by selecting the "Set default textures for category" option. You can override that if you select a vehicle and choose different textures. Again, these textures apply to the group icon above the leaders head and changes dynamically based on what vehicle the leader is occupying. The vehicle classes screen allows you to map vehicles to group textures. If the leader isn't in a vehicle, it uses the basic infantry group texture. I might, in the future, add the ability for the user to override the texture, during a mission, and set a specific texture for a particular group. Then it would ignore vehicle occupancy moving forward. For weapons, you select the weapon slot, then then the weapon. I did not add a 'default' texture based on slot because ... there's not nearly as many secondary weapons as there are primary and most of the primary weapons correspond to the basic infantry unit icon. I might add support for GL or maybe AA icons ... I'm not sure if ARMA has one. For now, the only icons that matter in the weapon classes screen are: iconMan, iconAT, iconMG. These textures are used for the unit itself and change dynamically based on the following conditions: 1. Leader (iconLeader) 2. Medic (iconMedic) 3. Secondary Weapon -> Matches to weapon class -> unit texture 4. Primary Weapon -> Matches to weapon class -> unit texture 5. Default (iconMan) The data for all of this is stored in the library files in <UserProfile>\AppData\Roaming\Athena\Library. 1. locationClasses -> cfgLocationTypes 2. vehicleClassCategories -> I forget what config I pulled this from but the values are essentially EdSubCat_AAs and similar. The 'default' textures for the categories are stored here. 3. vehicleClasses -> cfgVehicles filtered using classes in vehicleClassCategories 4. weaponClasses -> cfgWeapons filtered using type (slots: 1 (primaryWeapon), 2 (handGun), 4 (secondaryWeapon)) You can theoretically modify these files manually so I've saved them in a human friendly format. These files will be generated automatically, if they dont exist, when the extension is started for the first time. After that, their contents are loaded into memory and then saved to disk when instructed to do so via changes in the web app. If you manually change these files while ARMA is running, you'll have to restart ARMA. I'll be including these files in the releases moving forward though. There are some text encoding issues. I spent a little time trying to resolve them but I'm not sure if it's because I'm not writing a native c++ extension (c# .net 6) that perhaps the encoding isn't crossing over as expected. I spent some time on it but its low priority so I'm not going to spend much more time on it. You'll see some strange characters here and there in the classes and location names. It's a known issue.
  11. If anyone is testing out the latest version, don't bother with the unit and group icon setups. I'm redoing that whole thing.
  12. Added support for displaying units next waypoint. AthenaWeb_20221114_waypoints.png In desktop, I used dashed lines. In the web version, I'm adjusting the alpha/opacity. If you're further out than 1km, it's solid. Once closer than 1km, it starts fading until you're 250m out and then at that point, it remains at .25 opacity. The things I want to include before I release this in the workshop (separate item listing) are: 1. Map locations 2. Map anchors (basically your own set of locations) 3. Map markers (possibly including the drawings) 4. Map grid 5. Misc ui fixes (start/stop, resize, etc.) I'll add the following items later: 1. Orbat (unit list) 2. Hot keys (I think Arma exposed a key/action interface for mods) 3. Recording and playback 4. Map drawing 5. Community Server Also, another user requested a plugin system.
  13. There's a key in the keys folder in the zip. Have you added that key to your servers keys folder? I might be signing it wrong but I'm pretty sure that's all there is to it.
  14. That is also currently possible for a server admin/mission designer to do: expose both sides of the conflict to one or more players via those scope variables. If, via scripting, you set the value for 1 player to 16 (all) or 32 (leaders), they'll see units on both sides. I haven't tested it but I felt comfortable adding it because I figured, security wise, a mod would have to be whitelisted in order to be able to introduce a script that could modify the value. I should probably also add a listener to then compare the value to the allowed values but ... if you can change one, you can change both.
  15. Absolutely. Athena was a server side mod originally but it attracted zero attention. Much easier to get players to install it on their own than to rely on server admins. There are some assumptions in the current app about who the ‘player’ is that would have to be retooled but its entirely doable except…youre now running long running scripts on the server so thats a consideration. Marker visibility is also a problem. Only public channel markers would appear in athena because markers are only sent to the players in the target audience which makes sense from a security perspective but it is kind of annoying. In the end, nothing stopping a client from being an athena server which is what you did the other night.
×