Jump to content

biggerdave

Member
  • Content count

    634
  • Joined

  • Last visited

  • Medals

Community Reputation

29 Excellent

About biggerdave

  • Rank
    Master Sergeant

Contact Methods

  • Biography
    Little is known of the man they call Dave. Only one thing can be said for certain, and that is that there was already someone with the username "Big Dave", and he was confident he was bigger.

    In terms of height, that is. What you're thinking of _may_ be true, but we've yet to track down "Big Dave" to find out.
  1. Vehicle Interiors - Feedback

    Random question, but isn't the Marid a Turkish vehicle? (I know it is IRL, but is it in the ingame lore?) What's the logic for the control panels being in Russian?
  2. Oh, that makes sense. (But, why, though? I mean, is it better than the default mouse controls? 'cause I've always felt like the mouse steering has been a bit off since ArmA.1 compared to OFP)
  3. So, I was dicking around with control settings, based on Belbo's comments about mouse turning (still not idea what he's going on about, btw? There isn't mouse turning for commanders, at least on my instance?), and, it appears I owe you a minor apology, but, still; You need to have the command move (under the command settings) bound differently to the driver commands - so, if you have both driving and commanding bound to the same keys, you get sort of a "hybrid" command structure, that's a bit weird (so, you get the audio cues as if you're using the old method, but it controls like the rework, albeit slightly less precise). I've currently got it set up with WASD as direct control, and arrow keys for command controls (maybe numpad would work better?) - what's important is that you delete the common bindings, so, what you've got set for "command forward" and what you've got set for "accelerate" aren't the same! (ie, if you've bound W to move forward, you need to delete the binding for W to command forward) Ideally, yeah, there definitely needs to be, at the very least, an option to disable the direct controls for commanders, so you can bind them the same. (and maybe, while we're on the subject, a button for the commander to say "point the gun exactly here" (so we don't need to deal with the AI not being ""aware"" of the target you've just directly pointed them at) and "point the front armour exactly this direction", in lieu of trying to micromanage direction) (Turning behaviour is still the same between the two, though!)
  4. Didn't you just say you didn't want to talk to me anymore? =p (Like, the time stamps of those two posts are only 4 minutes apart! I literally spent more time than that making this post!)Then again, I guess when you don't proofread you have more time for changing your mind, right? Your point seems to be that turning under the old system involved just tapping the turn button and then hoping that your tank faces the right direction. I mean, you could have done that, I guess, but that's definitely not how it was intended to be used. Go boot up OFP, put yourself in as a tank commander, and hold down the A key, see what happens. (Spoiler alert, your tank is going to spin around on the spot until you let go of the key)
  5. Oh god, we've got to referencing paragraphs by number... this is going to be one of those threads, isn't it? Microdelay: How many commands begin with "Fo-" "Ri-" "Le-" "Ba-" that are likely to be used by tank commanders to their drivers? A full delay isn't realistic and again, realistically, tank crews can pre-plan their movements to prevent any delay in terms of commands being executed. Map commands: I'd say that's entirely relevant. You've just said you want a system where you don't have to constantly have hands-on-keyboard, and there it is. One click on the map, and off you go, then, as a commander can freely plan your next move or just wander off and make some tea (or, if you're a hardcore sim-er, you'll use the kettle in the decommissioned scorpion tank you've turned into the ultimate simulation PC!) Holding down a forward button vs. Pressing a forward button and then a stop button: Are both abstract systems. Neither one is more realistic than the other, because, realistically, you don't command a tank with a keyboard. It's completely meaningless to equate the two. Perhaps you "feel" one is more realistic, but, that's just like, your opinion, man. (you've said Coddlefield uses "hold down" commands, but pretty much all the dedicated tank simulators use "hold-down" commands, as well) Stopping the tank turning manually: Was never a feature in the old system. The tank would turn while you held the "turn right" key, and stop when you let go. It's exactly the same. Stopping the tank completely: Can be done in the new system with the "handbrake" command (I think it's "X" by default? I've remapped it to "Shift-S"). Also, you realise you're now complaining that the new system works too much like the old one, right?
  6. Right, but again, like I said, realistically, Tank commanders don't micromanage their crews. There's a lot of things that the AI simply can't understand that you'd expect between a tank commander and their driver (ie, "forward" might mean "follow the road a bit", not "just go straight directly forward until I tell you otherwise"). Is it realistic to have "steering wheel" control over the driver? No. But it's more realistic than a bunch of very abstract "direct" commands. I don't get your point about it being uncontested? Insubordination would not be a fun mechanic for the AI. Delay isn't realistic (and more importantly, it isn't fun!) - this is why WGL/ACE disabled it under the old system. Commanders and Drivers do understand each other. Tank crews train together for this exact purpose. (Moreover, even untrained crews can preplan their movements, to prevent delay) Again, a simple command, such as "bring us up behind that wall" is completely beyond the capabilities of the AI (and that's not even a complaint about the AI, it's a simple fact that machines can't easily process that kind of instruction from a person). It is near impossible to execute under the old system, but probably the easiest thing for an actual tank crew to perform. Or, an even better example "as soon as we fire, get us back behind cover" - a very simple instruction for a human driver, but with an AI crew under the old system, you'd potentially have about a 2-5 second delay trying to get the AI to perform this action - not ideal in a combat situation! And you can still give grid reference commands by using the map or command view. (I haven't tried it yet, but I imagine the "next waypoint" and "take formation" commands still work too) The only thing that's really changed is the micro-management commands. And, in the old system, you gave commands with the keyboard, too, so...? I honestly don't follow that last point? Turning vehicles feels identical in the new system, the only difference is it doesn't spam the message log, and you get the arguably more realistic "stop" when stopping turns than the old "forward". (Did this change between the dev branch and release?) If a system "feels" realistic, but it's impossible to perform actions that are completely trivial for real crews, then it's not a realistic system.
  7. ...I'm sorry, the old system was "realistic"? How exactly? The only thing that's changed is the micro-management controls. Realistically, tank commanders don't micromanage their crews, rather than saying "go forward exactly 5 meters, then turn exactly 30 degrees left, etc. etc.", you'd get something like "Bring us up to that wall", "once we fire, pull us back to cover". Since you can't expect the AI to be able to follow commands like these, we've just been given more direct control, rather than the clunky system that's been in place since OFP to pretty much everyone's chagrin. You still have proper commanding with the map/command view, if you want to sit back and let the AI do the driving.
  8. Flags don't need any configing. Just whack the .paas in a pbo and you're good to go. You can use "setflagtexture" to apply the new flag texture to any of the existing flagpoles. If, for whatever reason, you want to create an actual flagpole you can place in the editor, this is the basic code: class MyNewFlag: FlagCarrier { author="My Name"; class SimpleObject { eden=0; animate[]= { { "flag", 0 } }; hide[]={}; verticalOffset=3.977; verticalOffsetWorld=0; init="''"; }; editorPreview="\A3\EditorPreviews_F\Data\CfgVehicles\Flag_NATO_F.jpg"; scope=2; scopeCurator=2; displayName="My New Flagpole"; hiddenSelectionsTextures[]= { "\A3\Structures_F\Mil\Flags\Data\Mast_mil_CO.paa" }; hiddenSelectionsMaterials[]= { "\A3\Structures_F\Mil\Flags\Data\Mast_mil.rvmat" }; class EventHandlers { init="(_this select 0) setFlagTexture '\MyAddon\Whateverfolder\MyFlagTexture_CO.paa'"; }; }; For a billboard, you just need a new hiddenselection, you can either apply this to the billboard object in the editor using the "setobjecttexture" command (again, simply including a new texture in a pbo doesn't need any configing), or, if you need to make a new class (ie, for an object to be placed on a custom terrain): class MyNewBillboard: Land_Billboard_F { author="My Name"; displayName="My New Billboard"; hiddenSelectionsTextures[]= { "MyAddon\Whateverfolder\MyBillboardTexture_CO.paa" }; }; Just a final caveat, if you're not too familiar with the pbo format, you'll need to include a very basic config if you want to binarize your addon, so, something like this: class CfgPatches { class MyAddon //This should match the name of your PBO, for convience's sake, but it's not that important { units[]= {}; weapons[]={}; requiredVersion=0.1; requiredAddons[]={}; }; };
  9. AI Discussion (dev branch)

    Gonna be honest, I completely forgot vehicles were even in the game when making that post XD AFAIK, the only difference between Safe and Aware for infantry is they keep their weapons lowered and tend to move slower. (maybe they have lights on if they have them, which, tbh, kinda useless since they're pointing them at the floor. Good job illuminating that tiny area next to your foot!) As far as I can tell, Engage is a direct order, not a mode (like "Fire") - though, I'm only guessing that because you can spam it, while if a soldiers already in a mode, trying to issue the mode change order again won't produce any chat message. Yeah, ideally you'd want to be able to go from "sneaky" to "light'em up" with a single command (navigating through menus is a PITA, definitely not convenient when under fire!). Completely overhauling the system right now would probably break pretty every mission that uses waypoints, though... hopefully the next game has it completely overhauled... but dammit! I want fixed AI for the game I've actually brought! =p
  10. AI Discussion (dev branch)

    The problem is, as a squad leader, pretty much all the commands you can give to adjust your AI soldiers behaviour do nothing. Aware/Safe/Combat/Stealth are all virtually identical, since the AI will always transition to Combat mode when they know about enemies (regardless of how up-to-date that information is, or where the enemy are). Engage At will/Engage/Disengage don't do anything, since the AI always attacks targets of opportunity (sidenote, has "Engage" ever done anything?). Open Fire/Fire/Hold fire are the only ones of that much use, and even then, the AI will leave "hold fire" mode under... some condition? (As best I can tell, it's when the enemy spots them, which seems to suggest the AI can read the minds of the enemy?) I think the various bandage solutions applied to OFP's "AI wrangling" has kinda just made everything the same: the default behaviour (Aware/Disengage) isn't the "default behaviour". Since the AI are (quite rightly, IMHO) being expected to seek cover and engage targets of opportunity without explicitly being told to, but rather than make "Combat/Engage at will" the default behaviour, "Aware/Disengage" has been modified to make it what "Combat/Engage at will" used to be, which in turn has just made "Combat/Engage at will" useless. IMHO, it'd be best to move back towards how the AI handled these things in OFP, with some slight updates: -Aware has your soldiers keep a rigid formation, and prioritize following orders over everything else. -Combat becomes the new default, and behaves how aware does right now (so, keep formation when you don't know about the enemy, run around all tactical like when you do) -Stealth stays the same -Disengage doesn't attack targets unless told to. -Engage becomes the new default, attacks targets of opportunity, and doesn't use launchers unless told to. -Engage at will attacks targets of opportunity, and freely uses suppressive fire and antitank weapons without being told to.
  11. Premium Content Suggestion

    No, this is definitely something weird on your end. The icon is shown if an object is defined in a modfolder, not whether it's a premium asset or not - hence why, if you install something that adjusts base classes, like ACE, you get the ACE icon next to some base content. The only thing I can think of that might caused what you're seeing there is that something overwriting those vests and doesn't have a properly defined icon (though, then it should still sort properly?) or you've moved the character_F_mark.pbo file from the marksman directory to the base addons folder for some reason (maybe some "tools" might do this? Though, what this would achieve is beyond me)
  12. Arma 3 Aegis (Beta)

    Maybe some kind of futuristic mashup of the AK12 and 107? There was a very cool looking prototype AK12 with the counterbalancy device, that would be pretty to have ingame. (Top in the picture below) (Minor Bug, it seems IDAP's Kamaz seems to be getting a bit too into the spirit of the season, and has picked up a Ghostly Gunner - only seems to effect the covered variant, maybe an issue with how the BM-21 inheritance works?) Yes, I did notice this a month ago, and yes, I did wait until Halloween to report it just to make that joke. *Shades Descend* Deal with it.
  13. Hellfires don't work quite how you'd expect. There are two variants, the K variant can only lock onto laser targets - most helicopters have designators for this, but as far as I can tell, it's an uphill struggle trying to get the AI to use them properly. The L (longbow) variant locks onto radar targets, but be aware the only US helicopter that can mount hellfires AND has a radar is the Apache - I believe you can use the data-link added in jets to have another vehicle spot targets for you, though?
  14. Armaholic, how did this pass under your radar?

    The obvious solution would be for content creators to get together and demand Armaholic remove their work from the site unless something is done.
  15. Lib_truck_Base is definitely Iron Front - the classname is using the old Libmod tag.
×