Sunday, January 16, 2022

Rope based arresting system on Nimitz

 Rope based arresting system

With a recent update to Nimitz Experimental a rope based arresting system as implemented in Bon Homem Richard and MAAS previously was added to the Nimitz. It follows a description of the system.

The home of the rope based arresting system is in ttt_nimitzfunctions\fn_arrest_ropes, as well as the setup functions in jdg_carrier\functions\defaultInit.sqf.



fn_aircraftTailhook.sqf
    A compatibility function for BIS_fnc_aircraftTailhook that removes the hook up call in EXIT_CODE

fn_arrestEventsInit.sqf
    The system uses BIS scripted eventhandlers, which are set up here. The supported events are:
  • jdg_toggleTailhook
  • jdg_touchdown
  • jdg_abort
fn_caughtAnyWire.sqf
    Checks if the aircrafts tailhook is close to a wire. It relies on a hashmap of wires (_carrier getVariable "jdg_wireAreas") and then calls inPolygon to see if the tailhook is in the polygon defined by the wire.

fn_hasTailhookDown.sqf
    Checks if the tailhook is in down position. Either uses a simple tailhook mem point or whatever is defined in CarrierOpsCompatability.

fn_init.sqf
    Initialized the ctrl-shift-h tailhook toggle helper command.

fn_localWires.sqf
    When a plane from ttt_nimitz_planes is close to the wires of a carrier in ttt_nimitz_carriers this function is called where the plane is local to and checks if the tailhook grapples a wire via caughtAnyWire.

fn_toggleTailhook.sqf
    Simple function to lower or raise the tailhook, either via tailhook anim or as defined in CarrierOpsCompatability.

fn_touchdown.sqf
   The function that brakes the aircraft via setVelocity, pretty much a copy of BIS_fnc_aircraftTailhooks part of decelerating the plane.

fn_wireRopes.sqf
    Per frame function that checks if a plane from ttt_nimitz_planes is close to wires from ttt_nimitz_carriers. If close the localWires function is called on the system where the plane is located on. The use of two global arrays vs the use of nearEntities/nearObjects and so forth is done deliberately to give this function a speed advantage.

fn_wireRopesAttach.sqf
    Attach the ropes/wires onto the tailhook when the grappling of the tailhook to the wire was a success. Note that the ropes don't follow animations of the tailhook, unfortunately.

Cheers,
TeTeT

Tuesday, May 28, 2019

Nimitz update

Quite a while has passed with this blog being dormant. But the development of the Nimitz is not idle - slowly but surely we make progress.

Biggest news in the past couple of months was the move to Steam Workshop for the experimental build: https://steamcommunity.com/sharedfiles/filedetails/?id=1697731012 This experimental build contains the latest and not always stable additions to the Nimitz. Currently you can already see the upcoming changes to the island and lower deck on the port side, but not all areas are enterable and at places you fall through the cracks. Read, it is experimental and not considered to be stable enough for general use.

Speaking of the changes in the Nimitz, the Changelog contains various entries since the 0.102 release (https://tetet.de/arma/arma3/nimitz/experimental/Changelog.txt).

Functions to reset the cat and wires were added a while back, but never exposed to the player. This has changed lately and now you can reset the wires and catapults when things go wrong - mostly destroyed planes blocking cat and wire.
An oversight was the direction of air defenses on the carrier. In a previous build they were attached to the carrier parts, but now stand freely. This required a change in the direction setting commands, which has been done now.
The crane behind elevator 3 is now semi-functional, it can be raised and lowered with ctrl-w and ctrl-s, and turned left and right with ctrl-q and ctrl-e, if CBA is loaded. Unfortunately the crane is duplicated in the process, due to unknown reasons, so consider this feature to be very experimental.
The lower launchbar and repair actions were added repeatedly on dedicated servers. There is now some code in place to catch these duplicates and hopefully only one action will be available.
The island interiour has been restructured by Odyseus, extending to the hangar level deck and above below the island. This area is now a place of constant improvement and most likely once the renovation there is finished, Nimitz 0.103 will be released.
Joe provided us with a nice LSO platform which sits at the very aft section of the carrier now. It's not functional in any sense, but can be used for additional ambiance elements. Note that the current location is not final, as once the island work is completed, this section will be renovated next.
Some arma update broke the general quarters sound, this has been fixed by replacing the sound file and fixing the config entry for it.
Thanks to the USAF mod a new weapons cart is now available and has been placed on the weapons elevator. The cart carries a number of Sidewinder missiles and can be emptied and filled with player actions, if deployed stand alone (e.g. not on the weapons elevator).
The inheritance for the air defenses and radar of the Nimitz has been changed for the encore update of the Jets DLC and the air defenses are now more tightly integrated and more effective.
A landing statistics menu is now available from the islands ground floor level, showing who landed at which speed and which wire caught. This should help on multiplayer servers to see which pilots need some further practice and which are landing solid.
Another change is the printing of an error if the height of the Nimitz is not close to sea level. Various scripts in the carrier use hard coded values of 17.5 meters for deck height (hangar and other heights as well) and won't work if the carrier is spawned at a different height than sea level. Ultimately these hardcoded values would go from the scripts, but this requires more refactoring.
For landing experts, the vertical distance where the wire snatches you out of thin air can now be set in an Eden attribute of the carrier.
Also for landing, the IFLOLS range has been increased, so it can help landing on the Nimitz from farther away.

The next weeks will hopefully see the completion of the renovation of the island and decks below it, then some testing and bug fixing will be happening. Script wise the replacement of the hard coded height values might happen, and then 0.103 version is ready to be shipped.

Beyond that the general plan is to re-do the lower decks (2nd deck) below the hangar and to renovate the hangar and aft section of the carrier. On the scripting side, it's not decided what will happen next. We're open for suggestions and ideas on what else can be done for the carrier!

Friday, October 27, 2017

Plans for Nimitz in Arma 3 beyond 0.99

After the release is before the release, or so they say. Some ideas got implemented in Nimitz for Arma 3 0.99, but not all. So this is an overview of what might happen in Nimitz 0.100.

First, an already completed but untested task was the upgrade of the SAM systems, the Mk-29 Sea Sparrow launcher and RIM-116 RAM. Both systems now use a BI function to move the missile to the correct launch tube. Also they deploy Pookie's smoke script and generate some smoke upon launch.

Now onto the uncharted territory. With the advent of working radars with the sensors update as part of the Jet DLC, the anti air assets were already upgraded to use sensors. Now the Nimitz itself needs a long range radar to assist those weaponry and of course the planes. Work on this had started during 0.99 development, but was never completed. And when speaking of long range radar, I mean long range for the typical Arma 3 island, something in the range of 10-20 km.

The customization of the carrier for different versions of the Nimitz class is another topic to be discussed. The aft mast, located behind the island, is quite different between those subclasses and ideally we would have different models to show these differences. Further the island itself differs between the latest Nimitz class carriers and the original. And finally the numbers look a bit different on the real carrier than they do on our virtual one.

The hangar is quite an important part of the carrier, but lacks in details and 'liveliness' currently. I would hope for a complete overhaul, similar to what was done to the exteriour of the Nimitz already. It's undecided yet if ambient objects will be directly integrated, or left to the mission makers idea. Both approaches, an empty hangar, or one filled with objects, have their purpose and it's a hard decision which path to go down.

Sitting below the hangar is the 2nd deck. It can be considered a first approach of supplying additional rooms for communities on the Nimitz. The deck needs to be completely overhauled to look more ship like and equipped with objects. Mind you, there will be enough empty rooms available, so a mission maker can equip them as he deems fit.

Weapon carts are a needed addition to the carrier's properties list. The work on them has been contracted from the remaining donation money and should be available later in 2017.

For Nimitz 0.99 Shockley did a tremendous job at adding textures to the hull, which look more ship like than before. Hopefully this work can be continued for the flight deck textures and improve the textures further.

Script wise it would be interesting to add a teleport module for those player that don't want to walk/run around the carrier. There are already some memory points in place that can be used for that. Probably the best approach forward is to publish the nimspots lod, which contain those memory points, so mission makers can integrate their own teleport systems.

A completely different area is that of sounds. Late in the 0.99 release cycle the air conditioning sounds and engine sounds were added to the Nimitz. What's missing is now some general quarters alarm and other ambient sounds via speaker systems. Any suggestions are welcome here!

Yet another tech available in Arma 3 that has not been made widely available in the Nimitz are the Picture in Picture possibilites. The nautical's bridge monitor system is a good place to start on this, but more control rooms in the carrier's interiour could be thought of that get a view on the outside world via cameras.

Camera's are also found on UAVs, which are currently not exactly compatible with the Nimitz systems. The scripts for launching and recovering planes could use an overhaul so UAVs are supported as well.

The Tilly crash crane is currently a static property, as time to make it a carX simulation is rather scarce. Eventually it would be made fully driveable.

Last on this long laundry list is the IFLOLS system which sits untextured on the side of the carrier. Here a better texture, some light source magic and scripting is needed to make it a believable system.

As you can see from this post, we can really use some help in any of the above areas. Feel free to reach out when interested in helping, and join our discord server. There's also the possibility to hire modellers and texturers to assist with some of the above tasks. When doing a donation please let me know in the comment which part of the carrier you would like to see improved: Donate. The money raised so far helped with the following parts: RIM-116 RAM, Phalanx, nautical bridge, medical station, interiour objects, fuel pump, weapon carts (when completed) and new ammunition models.


Sunday, March 19, 2017

NDB Navigation

One of two aircraft related mods that I planned to do is the NDB non-directional-beacon navigation support; the other one is the MAAS system, which is still sadly lacking a nice model.

At the end of summer I got contacted by madsolosniper on the BI forums who had a mod idea for adding navigational aids to arma 3. When a few weeks later NightIntruder wrote me about his aircraft sign mod I sat down and wrote a couple of test missions at the end of September. One of them eventually was released by NightIntruder with his mod.

Then the project sat idle for quite a while. This weekend I then finally converted the sample mission into a mod, which still needs testing, especially in multiplayer.

The mod as it is now (2017-03-19) is quite minimalistic. It consists of an invisible NDB object and some actions on players to control the NDB navigation. The basic work flow is to add one or more NDB objects to the map at places like airfields, aircraft carrier, or the NDB building from NightIntruder's mod. On the object the frequency for the NDB can be set. In the mission players in aircraft can then change their direction finders frequency to that of any NDB. For publication of the NDB frequency for example a map marker or a note in the mission briefing can be used.

In the mission a player in an aircraft has three action menu entries:

  1. change frequency of direction finder to NDB frequency
  2. show the direction arrow on the HUD
  3. hide the direction arrow on the HUD
The implementation is quite straight forward and might be in need of optimisation for performance later on. In the config.cpp the "ttt_ndb1" class defines the invisible beacon object. It's main purpose is to keep the "Frequency" stored in a like named variable. Further it uses an init event handler to store the object in a global array (ttt_ndb_beacons) and initialize the mission event handler for showing the arrow on the HUD (addMissionEventHandler EachFrame). Also the Man class gets an extended init eventhandler to add the above mentioned user actions.

The init eventhandler for the Man class calls fn_addUI.sqf. The code there sets up the arrow for later use and adds three actions to the scroll wheel menu for the player. It relies on the locality of the global variable beaconActive and a few others to determine the state the system is in, e.g. if the arrow is displayed on the HUD or not. From the "Enter beacon frequency" action the dialog for entering the beacon frequency is triggered.

The init eventhandler for the beacon class "ttt_ndb1" checks if the global variable ttt_ndb_beacons is present. If this is not the case, it will be initialized and the mission event handler "EachFrame" is added to display the directional arrow on the HUD. Also the beacon object is added to the "ttt_ndb_beacons" array.

When the frequency is changed through the dialog, the "ttt_ndb_beacons" array is traversed and checked for the given frequency. If found, the new active beacon is set and the arrow points toward it. If not found, a message via "vehicleChat" is shown to the player that no such beacon frequency exists.

As this is pretty much my first attempt at changing the UI via mod, there might be other ways to achieve the wanted behaviour. Maybe some are much better than the way chosen, and I'd be glad to hear about them.



Wednesday, September 28, 2016

Nimit for arma 3 0.96 plans

With Nimitz for arma 3 0.95 out of the door, it is time to think of what is ahead for version 0.96. Currently we have a few open issues and bugs that we would like to address.

The Phalanx model has been enhanced by TheSnk4k3 and got a new set of textures, including secondary ones. It currently needs to be integrated into arma 3 properly. Also on air defenses we're re-evaluating the turning restrictions on the air defense assets, as some are still prone to hit the Nimitz itself. Some research will be done on anti missile defenses and if they are more successful than in the tests leading up to 0.95 will be included. Lastly in this area we would like to introduce a general quarters alarm that raises the alertness of the crews (set combat status to red).

Next on the list is the Tilly salvage and crash crane that is a static object right now. Making it driveable and operational in arma is quite an undertaking, we will see how far we get in the time frame for 0.96. If all goes very well it will be a fully functional carx and allow sling loading or at least attaching objects. Staying with cranes, the Nimitz crane should be made operational as well, we will be evaluating different UI approaches for it.

A new topic on the horizon are navigational aids for the Nimitz. In the form of a non-directional beacon aboard the ship it should be easier to find via a bearing indicator on aircraft. There is already a sample mission on Stratis (vanilla without Nimitz) available at http://tetet.de/arma/arma3/nimitz/experimental/missions/beaconFrequency.Stratis.7z Feedback is welcome.

In preparation for 0.95 we had two community members approaching us with a better IFLOLS experience, utilising arma 3 lights at the IFLOLS position on the carrier. Hopefully one of these will be made available at least as a mission if not Eden attribute for the Nimitz 0.96.

The holes that were pierced at the bow will be covered by some sort of gate, so the hull looks intact again. Via Eden attribute the opening can then be revealed when at harbour and closed when on sea.

On bug fixes the textures on the bridge will be inspected and reversed maps will be corrected. Further the bridge model will be split into separate models that hopefully can be reused for an airboss and prifly room. Unfortunately the donation campaign was not very successfull so far, so we cannot afford to source complete airboss and prifly rooms. Nevertheless thanks to the three donators who were very generous!

Foxone will provide an upgraded version of the test engine stand, which was previously dropped in 0.95. This is an all new model with upgraded textures. Again the sourcing of further ambient models hinges on further donations.

While we have no exact timing for the 0.96 release it will not land before December 2016, and is more likely to be in the first quarter of 2017.

Wednesday, September 14, 2016

Update on 0.95 and donations

The Nimitz has been upgraded in the past months to a new level. With the help from paid-for modellers from cgtrader and of course volunteers we were able to assemble a nice model of the carrier. The planned release date is end of September and we're currently looking for some more dedicated testers that help us to find issues with the Nimitz. If interested please drop me a private message.

Work done and completed so far is:
o Added nautical bridge (yeah!)
o Added fuel pump as object
o Added locker as object
o Added medical station equipment as objects
o Added briefing chair as object
o Added briefing screen as object
o Added pipes as objects
o Added air defense assets (mk29 sea sparrow launcher, Phalanx CIWS, RIM-116)
o Better Eden integration via attributes and menus

There is further work ongoing, namely the creation of a set of video tutorials for the carrier, the use of Eden attributes and menu items for creating ambiance objects on the Nimitz, the use of the IFLOLS system with Arma 3 lights and the creation of a help system within Eden. On medium term goals from a developers point of view, the module system will hopefully be completely integrated into Eden attributes and menus, making it easier to use.

From our point of view the use of payware models for enhancing the carrier has been quite a success. We would like to continue to use this method and hence look for donations for further funding. I have setup a paypal donation button for this purpose and hope we find some contributors.

Models that would likely to be acquired next are:
o bunk beds
o cage seat for hoisting guests aboard
o exercise room
o cinema
o shower room
o canteen
o fire fighting carrier car
o airboss room with flightdeck
o radar station / operations room / CIC
o interior rooms

The donation button can be found at http://tetet.de/arma/arma3/nimitz/donate.html

TeTeT

Tuesday, July 19, 2016

Future plans for the Nimitz for arma3

In a recent query on a Nimitz for arma3 youtube video the valid question was raised what the long term plans for the Nimitz are. In this blog post I try to answer this.

First, the development is driven by two distinct forces: one is the known issues (bug) list, the other is the interest and area of expertise of the involved developers. Ideally both would overlap and issues are resolved on the fly. In reality this is of course not always the case.

For example there is a number of texture problems and also needed model improvements on our known issues laundry list, but there is no active developer taking care of it. This of course limits the known issues we actually fix per release.

On the other hand we have areas which match the interest of a developer. For example Leshrack is on his way to improve the many scripts for aircraft and carrier operations in regards to multiple users and multiple carriers on map. I myself added some rooms to the weapons room level, as I was interested in exploring this part of modding. Then there are areas like testing which benefit from dedicated people like Moony, who basically gets to the see the changes first.

Besides the basically dedicated staff of the Nimitz, there are one-off contributors from the larger arma community who improve the carrier from time to time. For example in the beginning of the Nimitz for arma3 project, we had several submissions of texture sets for the hull and flightdeck.

In addition to the community effort, we're currently exploring the use of paid for models via a website named cgtrader. This is kind of a last resort move, as our calls for texture and modelling help could not be answered by the larger arma community. However, it's too early to tell if this approach will be successful.

Given this background it's hopefully clear that speaking of the plans for the Nimitz and the long term path for the carrier is necessarily a wishlist topic rather than a set in stone goal path.

Having said that, our goal is to provide a carrier that is operable in single and multi player arma3. It should support a simple and complex mode of operation, with the simple mode being intuitive enough for a new player to merely follow a tutorial mission and being able to utilize the carrier capabilities. The complex mode of operation tailors toward players not minding reading documentation and going the extra mile for a more realistic carrier experience. The current mode of operation is clearly a mix of the two - most functions are easy to use, but some like fueling an aircraft are not that easy to discover without reading the documentation.

Another huge topic for many player is seeing the carrier move through the water. If it ever will largely depends on the future development of the arma engine. We've seen with vehicle in vehicle transport capabilities that there's hope on the horizon. Support for the Man class (e.g. people) sticking to a moving and rocking surface is needed though.

Speaking of personal preferences, I certainly would like to see an integrated air defense system aboard the Nimitz. Currently an improved model for the sea sparrow is in the making and we might be able to source a phalanx or sea ram from cgtrader. In a first step these systems might be rigged as default arma3 anti aircraft systems. But in the future a working radar which controls these assets and is able to track missiles as well as aircraft would allow a player to play air defense coordinator aboard the Nimitz. In multiplayer this could be augmented by pilots on CAP as well as OPFOR pilots. Of course a Hawkeye to expand the radar capability of the carrier would be useful as well :)

Changing the focus from air operations to the carrier interior, we're currently working on providing a whole new deck on the level of the current weapons room. This work is driven by two motivators: one is the request for more empty space aboard the carrier for milsim units to use it as a base, the other is the relative unease of operation of the weapons elevator. So in February 2016 we started to explore the addition of new rooms roughly 2 meter above water level. This has resulted by now in a whole new deck under construction that reaches from the fore to the aft section of the carrier. Currently we're looking into the availability of floor plans to make these new rooms as carrier characteristic as possible.

Staying with the interior, there's a spot that's been under construction for a long time now: the island. While the stairwells from the arma2 LHD now give the island a refreshed look, the bridge and connecting parts are empty. Goal is here to use the sourced models from cgtrader to provide a nautical bridge and an airboss room. But as written above, we need to first see if this approach yields any success.

Coming back to future plans, above we've seen what are some immediate, mid and long term goals of the Nimitz for arma3 project. These should be sufficient for the next year. Beyond that, currently there'll be dragons. A lot depends on the future development of the engine and its capabilities in the air/sea area. But not everything: a long term goal is to make the carrier walkable from the heights of the island to the water level deck, another is the above mentioned integrated air defense capability, yet another is the creating of a simple and a complex mode of operation. But as it is with dragons, there's room for uncertainty - maybe some brave soul from the community steps up with her own ideas and those will alter the above set course!