morthon

So the idea is that I am placing trucks and tanks etc in the editor so I know the points I will later use to spawn vehicles actually have enough physical space to do so. The arrows are visual placeholders for the spawn points (I will make them invisible later). The reason I am not using markers is because I want to store data (variables) on the vehicles occupying the space inside the arrow entity. As far as I am aware you can't store variables in markers. I disabled simulation on the arrows because I am scared that they might hog performance, being as they are entities. I figured it couldn't hurt. In any case, I fixed my issue. This is what I ended up with: _findVehicleSlots = nearestObjects [[5100,5100], ["B_Truck_01_covered_F"],5100]; { _vehicleSlotPos = getPos _x; _vehicleSlotRot = getDir _x; deleteVehicle _x; _createVehicleSlot = createVehicle ["Sign_Arrow_Direction_F", _vehicleSlotPos, [], 0, "CAN_COLLIDE"]; _createVehicleSlot setDir _vehicleSlotRot; _createVehicleSlot setVariable ["slotType", "VEHICLE"]; _createVehicleSlot setVariable ["slotOccupied", "NO"]; _createVehicleSlot enableSimulationGlobal false; vehicleSlots append [_createVehicleSlot]; } forEach _findVehicleSlots; Now I have another question. I would like to give each arrow a variable name. Right now I am just storing them as elements in an array, but I would like to give them global variable names to then store inside another array. Is this inefficient or redundant? If you could give me advice, that would be great!

Hi, so I'm trying to spawn vehicles on predefined points using forEach loops. I need to be able to check what types of points I am selecting in the script, because i have points specifically for light vehicles, tanks and planes respectively. To do that I want to use setVariable to the objects I'm using as reference so I can filter dynamically. So far, my attempts to add variables is only producing an error: Undefined variable in expression vehicleSlots (an array). Replacing the vehicles with arrows (placeholder) is working perfectly. Any help would be appreciated. _findVehicleSlots = nearestObjects [[5100,5100], ["B_Truck_01_covered_F"],5100]; vehicleSlots = { _vehicleSlotPos = getPos _x; _vehicleSlotRot = getDir _x; deleteVehicle _x; _createVehicleSlot = createVehicle ["Sign_Arrow_Direction_F", _vehicleSlotPos, [], 0, "CAN_COLLIDE"]; _createVehicleSlot setDir _vehicleSlotRot; _createVehicleSlot setVariable ["SLOTTYPE", "VEHICLE"]; _createVehicleSlot enableSimulationGlobal false; } forEach _findVehicleSlots; Cheers!

Hi, does anyone know how to activate DAC zones from within a script? I"m trying to build a system that spawns zones and their content dynamically. I''m having trouble defining the zone.

The halo 3 marines were released in the OPCAN modpack. Some time ago, the OPCAN mod developer lost all his files in a hard-drive failure and has been steadily rebuilding parts of OPCAN since. The additions he made to the Halo 3 Marines were not part of the content he wished to restore. However, the OPTRE developers have plans to include the Halo 3 Marines in a future First Contact release. I don't know when that will happen, but the H3 Marines will become available again at some point in the future.

Some raw test footage: Added: - Running with One-handed firearm (spiker). - Weapon raising/lowering. - First weapon reload animation (for the spiker): Sadly the first person view doesn't look anything like how it's supposed to. Will work on grenade throwing now and then walking and running with weapons lowered.

Update: After ironing out the configs, they are now fully in-game and can turn and fire. Next step is to add in movement.

Update: back in-engine again! Textures came out pretty nicely so far, if I say so myself. Textures are still WIP though.

I want to do a complete redo from scratch in the future. Probably including more attachments, more varied uniforms set-ups and gloves. Well, zombies and demons has a script for knocking cars around...

Brute Minor helmet and armor high-poly models done :)

Hi, long time no speak! Found some time this week to work on this some more. Finished the first (of two) Brute uniforms this week, took me about 16 hours total. Contrast that to the Halo 3 Marines which took me weeks to complete. Also started work on the new and improved rig for the Brute and I'm preparing to get everything back in-engine. The Brute Minor character is pretty close to being done :) Will try to start doing the armor pieces next. Cheers!

I don't know yet. Personally I wouldn't mind if they just spoke english like in Halo 3, but it would of course be more realistic if they had some sort of alien tongue. But yeah, I'm helpless when it comes to audio design, so I might need some help with that later down the line.

Update! Behold the new proportions, I'm very happy with this and I will stick with this, I call it the Super Brute. I tried out enlargening them to 2.80m (accurate to the lore), but it was just too big for my taste. So I scaled them back down again, the final height will thus be 2.60m (the height they actually are in H3 and H3:ODST). This looks just so much more satisfying, more animalistic, less human and most importantly, much more menacing! This also means that the 3D art concept phase is done and I will start to finalize the model and add high-poly detail in-between animating and start to texture it! This does mean I will have to start over in terms of animation, but its fine. I have been trying out alot of efficient animation techniques to take shortcuts here and there and the results were good! Comparison: 2.80m was just too large...:

Update! This is where I am right now. I'm still focused on getting basic free standing motion. Right now, forward motion is pretty much implemented, so walking/running/sprinting forward in addition to moving forward-left and forward-right. Literally everything is still work in progress and the animations are quick and dirty test animations just to I can figure out the system :) I'm gonna be doing some work on the proportions too. They just don't feel satisfying enough to me, they need to be beefier, more menacing, less "human". And I'm still undecided about the size. I might try scaling them up a bit to proper 2.8m and see how that looks.

It was more like I just didn't know that "-" characters are forbidden in the model.cfg while they work fine anywhere else. I'm otherwise pretty good at detecting and fixing syntax errors. I will refrain some using them altogether from now on. You learn more every day! Very happy that it works now. I expanded the initial animations with a running and sprinting animation. I'm still 100% in the testing/experimenting phase to figure everything out, though, so everything still looks horrible. While I understand the animation system and its implementation now, there are still unknowns that I will now focus on. Things like: - Procedural animations - Animation blending (layering) - Ragdolls - How to properly implement memory points into the skeleton (cameras, axes for procedural animations etc) - Integrating proxies into my custom skeleton (for weapon location, holstering etc) - IK Chains After those tests are done and figured out, I will start over and completely redo the skeleton and adjust the proportions of the character, settle on a final scale (2.6m now, feels a little short ingame, still undecided) and lay the groundwork to actually finish the character model.

The problem is fixed thanks to some aid from Mondkalb. It turns out my model.cfg contained a "-" character and ARMA apparently doesn't like that :D