Jump to content
Bohemia Interactive Forums

Apocal

Member
 View Profile  See their activity

  • Content Count

    232

  • Joined

  • Last visited

  • Medals

Posts posted by Apocal

  1. Posted

    Line-of-sight is computed by the tank's hull. Put a tank hull down behind a Jersey barrier and enemy tanks and infantry will never shoot at you, assuming that they are on level ground. At any rate galozhar, why are you so obsessed with finding reasons it can't be done without unrealistically massive changes?

  2. Posted

    What's sad about the grass is that with it disabled you see how "flat"/smooth the terrain is, and then remember the grass is just an overlay and the terrain under it is still "flat"/smooth even when grass is turned on. It's not just hurting the looks, it's also hurting the gameplay because outside of towns there's absolutely no cover anywhere other than trees and the occasional stone wall or extremely rare rock. The terrain surface definitely needs more stones/rocks/bumps/etc, much more than it needs the massive foliage that doesn't even get rendered further than ~45m.

    OFP originally had a setting for this (setTerrainGrid), affecting bits of microterrain. It lagged horribly and everyone set it to the flattest possible setting as I recall.

  4. Posted

    Except IRL you can also fire it from 10km, while in game only 2-3km or so (more or less depending on some unclear parameters). In the game you would pass the target in 30s, making mavericks useless, and still very unrealistic (they are not useless IRL). That's what I meant when I said some realistic features need to come as a "package" or they won't work.

    You can certainly lock on at 6 or 7km in-game and use that.

  5. Posted

    If they're going to make realistic target acquisition they're also going to need to give weapons their RL ranges as well. When you can only fire a maverick from 2-3KM you might pass the target by the time you manage to do all the required actions, which is obviously not a problem IRL where you can fire from much further away.

    I'm all for more realism, but some realistic features require the "whole pack" and won't work if implemented by themselves.

    As easily acceptable substitute would be a Maverick that had to wait 10-30 seconds before it would go from Acquired to Locked. Real life, it takes about that long (occasionally longer) for the IRMAV to 'learn' what it's target looks like.

  6. Posted

    I still cannot place the NATO-symbols in the editor unless I add the module to the map. I'm using version 1.03. Haven't tried the BETA-version, though. Until today I honestly believed that adding new markers was the sole purpose of the Military Markers Module. Hence I didn't delve very deep into it's inne workings. I supposed I would have noticed that they were missing if I would have played around with the HC module, but I've hardly touched that one so far. Been too busy meddling with the ACM, SOM and Artillery.

    Out of curiousity,do you have the NA STEAM version? That's what I have and it seems around these parts more people understand what the symbols mean (bigger wargaming market perhaps?).

    I've been looking to the scripts from MARTA but I can't get them to work.

    What I want is to have NATO symbols showed over units like in HC mode but without HC thing and without having enemy groups showing on map . I'm sure this can be done somehow , and may-be with MARTA i could acheive this. But I need some help.

    Try setting one of the true values to false?

    setGroupIconsVisible [true,true];

  8. Posted · Edited by Apocal

    No new symbols for me Gaia. It appears to be either A) enabled by default or B) not initializing at all.

    I suspect A) because I have all the rectangular NATO infantry, armor, artillery, etc. symbols available, without any modules placed. If the "Military Markers" are b_armor, b_artillery , the various group_n, etc.

    If they are different, than those, then the module is simply not initializing for me, even with your init line.

  10. Posted

    Hi,i know there was allready plenty questions on the Arty Module,i also visited the BIKI,but no success.

    I wanna get firesupport from 2 mortars on the OPFOR Side as request per Radio,but i dont get how do that.OPFOR dont got mortars so i have to use empty,and "beam" the AI in.Maybe thats the problem..?

    Help would be much appreciated.!!!thx

    OPFOR do get mortars. Look under OPFOR-> Russia (or Insurgent) -> Static -> Podnos 2B14.

  16. Posted

    Has anyone else noticed that smoke has become seriously limited in both it's intensity (obscuring) and the length of hang time? Almost to the point of worthlessness? I'm about to test in single-player, but it seems seriously nerfed, which is somewhat surprising because it was something BIS did right; lagfree and realistic smoke.

  21. Posted

    So if people are interested in a combination of both, I could try to make something like that again, but I'd need some help on the realism side since I've never been around mortars in the army.

    People are interested. The realism side you covered rather well, adjustments are made by mils, deflection and elevation.

  22. Posted

    I just want tank drivers to have more than one vision block. Jesus man, it's harder to maintain situational awareness as a buttoned-up tank driver in ArmA than in real life; and that is saying a lot.

    Additionally, all personnel carriers in ArmA had 3D interiors. Stryker, M113, BRDM, BMP2, etc.

  23. Posted

    I don't really consider map markers "realism." We use 8-figure grid coordinates which is 10x10m. The sheaf should be bigger than a single explosion too. I'm really not a fan of the default system.

    The BCS I worked with actually lays out it's own "map markers", in fact the same markers are already in ArmA2; the red "+" symbol. Although it was a monochrome display with nothing but grid refs, when a mission was being processed it'd go from one + marker to however many active guns we had, in whatever sheaf we were shooting, generally a 100m or 200m circle. You'd verify the sheaf and dispersion was correct, then send the data to the gun line.

    Standard call-for-fire was a six digit grid ref, if you wanted to hit a point target it was fire and adjust. We used ten digit grids for registration, but that wasn't the kind of thing you'd do at the level of combat ArmA focuses on.

    A player acting as FDC marking up the map with aimpoints for his pieces to aim at isn't terribly far off from reality. An FO marking the map on the other hand... yeah that's somewhat arcade.

    SIDENOTE: WHY THE HELL DO PEOPLE ALWAYS USE THAT BIG-ASS CIRCLE X MARKER TO CALL FOR FIRE?! DO THEY REALIZE ITS HARDER TO AIM WHEN IT'S A HUGE-ASS MARKER INSTEAD OF A DISCRETE DOT OR PLUS SYMBOL?

  25. Posted

    The ARTY module is written in FSM.

    You can modify it yourself now.

    Add keyboard use in addition to mouse control.

    He is requesting some kind of fine control in addition to the current coarse control. Anyone who used Jones' real artillery back in ArmA wanted the same after the pain of trying to get a 50m adjustment dialled in on a target 11km away.

×