It has been a while since I updated my Takistan Insurgency mission. I've recently begun rewriting a lot of the code and making large changes. Much of what was going to be included in my unannounced counter-insurgency simulation mission will partially be included in this upcoming update. Some noteworthy changes will be persistent grids, revamped civilian AI, improved performance, better interaction scheme, gathering intel has been slightly redesigned and will receive a much larger redesign in the future, bug fixes, and a lot more.

The update won't come as soon as Christmas or New Years, but hopefully shortly after. January and February will be very busy months for me due to job-related work, but I feel like I have enough stuff done to make a push for a release in a month or two.


I've begun the implementation of optional (Disabled by default) Side channel support. If the mission designer manually enables Side channel via the 'CFG.sqf', then all players will be able to communicate on Side channel. The mission designer will have the freedom to enable/disable voice and/or text in that channel. The only restriction will be to have a radio equipped. Also, the update to AFAR will also allow support for TFAR, RHS, and CUP modded radio backpacks, allowing players with a radio backpack from one of those mods to gain access to the Support Channel.


Expect a quick YouTube video soon on a very basic tip that is useful to those who like coding in the debug window without CBA.


Honestly, I have way too many other Arma-related script and mission projects I work on... Futbol, Addon-Free Zombie Apocalypse, Medieval Fantasy RPG, Civilian Traffic (Attempt at writing heavy traffic with the lowest performance impact), and Counter-Insurgency Simulation (One of my primary focused passion projects) are a few off the top of my head, but there are lots more. Maybe someday I'll be able release them.

The latest update to AFAR[drive.google.com] introduces my first implementation of Zeus compatibility and several major & minor fixes. Next update, whenever that may be (Focusing on other projects now), will likely include optional Side channel support and hopefully more bug fixes.

Created a video that was requested months ago; redid a video on how to apply an image to a texture, using both setObjectTexture and applying it in the editor (If the object allows). Will try to upload it sometime this week. Downside is that it's 10 minutes long...

Other than that, not much else to report. I'm working on two of my unannounced projects, but that's about it. Did a little progress on Combat Realism Scripts, mostly with the flashbang (I'm rewriting it) but it's still ♥♥♥♥♥♥.

This month, version 0.92 was released but reportedly still had major issues. I've since fixed all major bugs, except for one, in AFAR that I am aware of. Version 0.93 will come sometime in August, which will introduce a lot of critical fixes and optimizations, including Zeus compatibility! I finally caved and added the support. Right now, I'm working on fixing 1 more bug and finishing the integration of the Contact DLC radio backpacks. Yes, RTOs require them now. If you don't like the annoying DLC advertisements when wearing the backpack, buy the DLC or don't be a ♥♥♥♥♥♥♥ RTO.


This month I rewrote CRS in a few ways; the way it initializes, settings you can configure in the 'CFG.sqf', optimizations, and bug fixing. The "framework" of CRS is still incomplete and being written in a way that it'll make it easier for mission makers to implement/utilize. Also rewrote some of the flashbang code to be more optimized and am working on changing what it looks like, as well as improving it's effectiveness (In the sense of making it actually work...).


<CLASSIFIED>


Aside from creating a few furniture layouts for Livonia houses so far, I recently started on partially rewriting all furniture layout scripts to handle the setDir of code more efficiently in a single line of code, rather than on every line after creating an object. Efficient code is good code. The #1 issue with PF is the scheduler is almost instantly getting too full when spawning furniture, which is causing massive delays between when code executing. I'm heavily focused on optimizing to alleviate this problem. Will likely reduce the number of furniture objects per house or set a cap to really fix it. Stay tuned for the next SITREP to find out if it works.


No progress made on this script; the projects listed above have been my main priorities. There's also a couple other dumb side projects I've been working on, such as a MP soccer mini-game mission that I'll be releasing soon, but that's about it.


Lots of progress made, lots and lots more to go...


More videos coming soon. Will fulfill a couple video requests and have a list of like 50 "Optimizing Arma" episode ideas I can do, but always torn on how to explain it quickly. I need to work on shortening my videos too, 6-10 minutes is too long... bought a video editing program for like $7 but will probably never use it.

I'm gonna skip the usual format today and just vomit out loads of information. If you prefer more detailed info like this or prefer the older way (but maybe need to get more into details than short vague updates), let me know.



A tremendous amount of progress has been made last year and this year on:

• Addon-Free Arma Radio
  
• Combat Realism Scripts
  
• Insurgency (Altis, Takistan, etc.)
  
• Phronk's Furniture
  
• Simple IED Script
  
• <Unannounced Project 1>
  
• <Unannounced Project 2>
  
• <Unannounced Project 3>

As a quick disclaimer, "unannounced" doesn't mean I think I'm a AAA developer trying to withhold information for legal or hype reasons; they're unannounced because they're not at a state I'd like to present them in (I have a bad habit of releasing untested buggy content as it is) and it'd generate unintended hype for something that won't come for months or longer. When I announce them, the release will be within the foreseeable future and I'd like the reveal to be a bit more appealing. TL;DR: Better to announce a project that I can actually release with screenshots/videos displaying what it is rather than just a wall of text/speculation of what it will be.


A much more stable version 0.91 has been released. This fixes a ton of bugs, includes some rewrites, better efficiency, better optimization and configurations. Is it bug-free? Almost, but no. A couple bugs have since been reported and I'm looking into fixing them. Even more feature additions are planned in the next update (No ETA, not a priority right now) such as extended interference, which is basically more radio static and player's voice cutting in/out while transmitting with a weak signal. More variables which influence the signal will be introduced also, to work in hand with this feature.

The two top requested features is "made it a mod" and "make it Zeus compatible." As stated in the FAQ, these are low priorities but I will eventually get to both of them. It is a higher priority to fix bugs and finish adding remaining features I'd like to implement.

Also, AFAR will support the new radio backpacks for RTOs when the Contact DLC releases.


These scripts currently SUCK. Not only are they buggy, difficult to implement, and overly simplistic (Feature-wise), the premise of the code so far isn't realistic. It's the main reason why I stopped working on the code, because the direction of the script was too arcadey for me to enjoy even writing, let alone playing with. I've decided to rewrite all of the code to focus more on the realism aspect. Additionally, the new features I intend to add will enhance realism and therefore immersion. Each feature can be easily disabled via the "CFG.sqf" the scripts come with and will be much easier to implement stuff like blast fragmentation, backblast, disposable launchers, and more for individual units such as placed/spawned AI.

What are the drawbacks?

• Rewriting code takes time: I don't just rewrite the code, I redesign it. The code needs to be more efficient, modular, optimized, and realistic.
  
• Realism = more complex code. More complex code means heavier performance impact. Performance impacts means more optimizations and redesigning/rewriting until it runs at a tolerable level.
  
• It won't be for everyone: A lot of people prefer quick & simple video game features that they can execute quickly without much thought process needed. I do not cater to those crowds. I'm obviously reinventing the wheel here though; ACE, AGM, and other mods have been around for a very long time. This just aims to be a easy-to-implement scripted alternative, either for closed communities or public servers.

I want to develop features which enhance immersion for all players, including veterans. The little details matter. With the consultation of combat veterans, I'm trying to script all sorts of features to pull you into Arma's infantry simulation and expand on it as best as I'm able to.


My insurgency missions have sort of been on hiatus, but only publicly. Behind closed doors, I've worked on a lot of code which will effectively transform this into another project. The premise of an insurgency will remain the same, but the goal and how it is achieved will be much different. I'd love to get deeper into the details, but unfortunately I can only tease that I'm working on simulating an insurgency more-so than the current shoot-em-up version I have out now. It won't be for all audiences. It's just a passion-project at this point and IDGAF if it's fun or not -- I'm striving for realism and immersion now and leaving it at that.


To call the changes this set of scripts received as "massive" would be an understatement. The code has since been completely rewritten for much better optimization and expansion. For optimization, the code runs much faster and efficiently -- keep in mind it is designed for a dedicated server to run, but still works fine in SP & MP.

Optimizations include changes like completely removing any references to attachTo, converting (nearly all) simulated furniture objects to simpleObjects & superSimpleObjects, completely written to run only server-side, better utilization of commands, and more still to come! The one major downside I've faced since the start of the project is that the furniture, so far only on dedicated servers, doesn't like to always spawn all at once or when it's supposed to. Right now, there can sometimes be a delay from seconds to minutes before you see the furniture spawn -- this has been an issue even when the furniture was simulated objects and persists even as simple and superSimple objects. It's likely a bottleneck by the engine or code oversight, but hopefully there's a workaround. Aside from that, performance has been fantastic.

As for the expansion of the script, I've made the code even more modular than it was, added much more furniture layouts (And plan to add way more), improved placement of objects in "house" layouts which don't have a modeled floor like shanty sheds, and a new large feature which will tie into unannounced project 1 as well. This expansion plus the optimizations coming™ will absolutely be worth the wait. It has been a lot of work and still requires a ♥♥♥♥♥♥♥ ♥♥♥♥ ton more work, but it has come a long way and is beginning to take shape of what I wanted to develop it into all along and mold it into the vision I had when I first started coding in Arma -- and more.

Not trying to hype it up, but a lot of work has gone into it. Revised the furniture code at least 4 times, the "expansion" has been rewritten at least 3 times, tons of bug fixing and optimizing, lots of proof-of-concepts became actual fully implemented (But still need more work to be final), and the goal is to have it be easily ported to any map with building classnames the script supports. So far so good, but much more work still has to be done before I can be satisfied with a "complete" version worth releasing. Due to all the gigantic changes, releasing it in this incomplete phase would produce lots of bugs and the feel of what I'm going for hasn't been achieved yet to my vision/standards.

Yet another script which began as a tiny and simple script with little ideas behind it, is now expanding into something more. Don't worry, it'll still be small and easy to add to your missions, but I want this to divert from your usual IED script. This means the IEDs will no longer only be confined to road segments, but inconspicuous objects as well. They won't always be so obviously placed and the types will vary. Additionally, I'm considering adding a simple triggerman who will watch the planted IED (Unless it is a pressure-place IED) and detonate it when Blufor enters the blast radius.

I'll go more into these features next time, but expect IEDs to also be hidden in dead animals, wrecks, barrels, near rocks, and more. Blast fragmentation has also been added. Lots more work to be done, but I'll go more into the details as I complete more of the code.


[CLASSIFIED]


Zombies. Nothing exciting to see here, I'll show it off when it's polished and ready.


CQB AI. Proof-of-concept of implementing a set of scripts which enables AI to autonomously breach & clear buildings. Similar to Johnnyboy's goal, but mine will aim to be autonomous and aim for tactical realism as best as possible, but likely be confined to fireteams (And smaller). I've made a lot of headway on it but the autonomous part is the barrier I'm trying to figure out. It is very possible this can leave proof-of-concept phase and reach a full implementation, it just takes a lot of time to design and code. If I do come close to ever releasing this, I'll upload a video or at least make a post on the approaches I tried and why I chose the one I eventually stuck with.


I really wanted to learn the Fusion engine's "Enforce" script language, but after giving DayZ a try 6 years since I last played when it first came to Steam, the game was still riddled with bugs it had back then (Warping / teleporting AI through walls, floors, and ceilings) so overall I wasn't impressed. It came a long way in the optimization and visuals departments, but those pathing/collision bugs were too disappointing. Unfortunate to see that despite Arma 4 having a completely new engine, it will still have some of the same bugs which plagued it since OFP. Mind boggling. Looks like I'm sticking with SQF & Arma 3 until then.


Despite YT becoming yet another anti-freedom platform, I still plan on making videos and uploading them there (Unless I find a better site, might even decide to go with just uploading to Steam honestly). Just haven't been in the right mood to make videos. Maybe I'll do one soon? We'll see. I do need to remake my AFAR videos actually...


Anyway... that might be the biggest post yet. Tried giving as much info as I could without giving away "too much." Again, if it's too much to read and you prefer the shorter format, let me know.

I'm alive! 2018 was one of the most life-changing years for me, for the better; I moved half-way across the country on a whim for a job opportunity, live on my own, got a car, removed a toxic person from my life, and made a lot of progress with coding. Lots of awesome experiences too.

With that said, I've been coding in Arma this whole time during my hiatus, primarily focused on my secret project(s). I may need to do a major rewrite of said project, so don't expect an announcement on it anytime soon.


Due to popular demand, I've decided to continue working on the radio script to (temporarily) remove the distance requirements and radio noise effect. This should help keep the script viable on addon-free servers while still preserving some comms immersion. To do this, I need to do some code rewrites for efficiency and optimization. Expect an update to release within a couple weeks, tops.


Unfortunately, I put this on hold due to my need to rewrite everything for better multiplayer compatibility. Works fine in singleplayer, but I am not satisfied with single-player-only compatibility.


Too many noteworthy changes to talk about. No release date even in my mind, but I'm working on a version for Altis, Tanoa, and Takistan.


Lots of rewrites for better modularity and efficiency.


Started rewriting the code again for better efficiency and multiplayer compatibility. May also include basic AI compatibility as well.


There's a lot more that I'm working on, but those details will come later. Thanks for stickin' around.

~ Phronk