Jump to content
Bohemia Interactive Forums

_Pingu_

Member
 View Profile  See their activity

  • Content Count

    45

  • Joined

  • Last visited

  • Medals

Posts posted by _Pingu_

  2. Posted

    Here they are, features are:

    - Simulated shrapnel as well as blast damage.

    - Peep sight for sighting in.

    - Safety mechanism so that you can safely blow a predetermined set of mines.

    - Command detonated up to 200m and tripwire (Illegal in many armies).

    - Anyone (including enemies) may rotate, attach tripwires or disarm any claymore.

    - Scripts included for mission editors to place armed claymores anywhere (pointing anywhere too) with thier own triggers.

    Please note! This script does not use extended event handlers and will require you to place a claymore ammo box in the mission somewhere to have them work properly.

    I consider this release quite stable, it has gone through two betas and private testing. All mods are free to use and modify this addon, all I ask is that credit remains mine and any useful modifications are made avaliable to the community again under the same pretense (I'll incorporate any good changes). I'd suggest that vietnaam mods take out the night vision for the peep sight and modern warfare mods remove the tripwires if it's not legal. Night vision can be removed in peep_sight.sqf, tripwires can be removed in proximity_loop.sqf. If you need help, PM me.

    Here's the mirror for now, will update when someone mirrors it properly. Please call it 'claymore', the version is 1.0.

    http://www.armaholic.com/page.php?id=2624

    http://armed-assault.de/downloads/claymore-10.html

    http://prison.tibet225.server4you.de/ww2pn...._id=425

  3. Posted

    Blackknight.au - whatever you will tell about my old addons, my old poor weapon pack - they were not copy+paste addon :P

    so do not compare models made in oxygen, there textured before TOOLS were released with model made by "copy sight, past to another model, save as..."

    and remember that i also made things like an Alien APC, like vehicles pack (first BMP-1 made for ARMA), i made first working and engaging chopers before BIS made fix in patch... :P

    You should know very well that the technical prowess and sheer effort that goes into a mod by no means corresponds to the quality and usefulness of a project. If I give a retard O2 and he puts out a sub-par modification, sure it may be an acheivement for him (and I am by no means belittling your work) however! This does not make his mod any more impressive through the eyes of the user.

    I don't appreciate you insinuating that I am incapable of that which you claim you are.

  4. Posted

    For the last time, I am not saying that this looks like a MAG 58 from the factory, or an australian one, or a belgian one or ANYONES MAG 58. It is a MAG 58 that has been modified and called an m240. I call it a MAG 58 because that is still what it is! The classnames are all m240_acog, m240_aimpoint. Now if we could all shut up about these stupid different ways of communicating the same fucking thing that would be great. And yes I'm swearing, and I hope you're all relsilient enough to withstand such abhrasive language and not try to use it as an argument. You, vilas and many others don't seem to be interested in the fact that I at no time said this was not an M240. To reiterate, it is an M240 which is a MAG 58. I like to call it the latter when just talking about it, however if you look at all the classnames, descriptions and even go so far as to look at the damned pbo name half of you would realise I'm calling it an m240 anyway.

  6. Posted

    Look, we don't use FN MAG 58s as they arrive from the factory in australia either, we modify them. We even call them GPMGs. We just call them MAG 58's, it's like calling a shortened barrel m249 a minimi. Who honestly cares? All the classnames are m240 so can we please just agree that I'll call it a MAG 58 and you all can call it whatever the fuck you want. I can't stress enough that it REALLY DOES NOT MATTER.

  10. Posted

    Thanks for that dmarkwick, works great. I'm just getting it flickering right now, I tried to play with the smoke but failed utterly. Is it easy to get it to originate from a much smaller point? Right now it looks like it's smoke blowing out of a large hole in a ground, I want a thin stream making an inverted cone coming from the top of the flare. Check the video in the first post, that's exactly what I want, is it possible? If not, can we at least make the particles smaller and the cloud itself less fat?

  12. Posted

    nice one, maybe an acog for the m249 as well?

    also the different names are because of different countries military designations.

    There's already an m249 acog in the AimPoint desert weapons pack.

    Reguardless, I'm not going to work on the minimi while the MAG 58 is still found wanting. I've still got an aimpoint and tripod to do.

  14. Posted

    I'll certainly give it a listen, maybe we can even use it in the next version of the sound mod if it's better.

    From what I understand though the m60 is a much louder and beefier sounding weapon.

    It should be twice as loud as the stock arma sound, perhaps try listening to it from a distance? I suppose you mean the volume of the actual sound though.

    Thanks for the feedback.

  16. Posted

    Thanks to the newly released models I've stuck an ACOG on the MAG 58 and created a calibrated sight based off NWD's scope fix (thanks) which goes out to 1 kilometer.

    I've also fixed the ejection port, now the casings come out the bottom of the weapon (no link out the side though unfortunately). The weapon is more accurate too, an 8 round burst at 500 meters should not be going wildly off to the side by up to three meters, or maybe it's just simulating American marksmanship? Finally, I've fixed the recoil which now goes up instead of down.

    Sounds come from our (AACF's) sound mod.

    Do whatever you like with it, it's got that BIS licence whatever that is I suppose, so long as credit remains mine.

    Class name is m240_acog, addWeapon it to a weapons US crate.

    Here it is, mirrors appreciated:

    http://www.armedassault.info/index.p....lang=en

    http://www.armaholic.com/page.php?id=2813

    edit: Oh, and the reticle is for the 1.09 patch. Not sure if ballistics have changed so it may not work in 1.08 as well.

  19. Posted

    I've been working on a tripflare, everything is done and working aside from the effect. I currently have it spawning a flare a couple of hundred meters above the tripflare, which isn't right as it's a ground based tripflare not a parachute one. I'll probably end up releasing two versions of the flare (ground and parachute based) but I need help with the effects for the ground based one.

    I have no idea how to do effects at all, does anyone know how to get something looking like this? The smoke is important, multiplayer compatibility is imporant too (though if it's hard I can probably get the detonation code to run on all clients as it isn't as imperative as it is with claymores for them to detonate at the exact same moment).

    http://www.youtube.com/watch?v=w3FCDM0kF8w

  20. Posted

    Yeah that's really the only way to do dust & sand kicked up by kinetic shock. Trying to get it to zoom out and suddenly stop is impossible with the ArmA particle system, I find that your mind usually fills in what "must" have happened when dust suddenly appears smile_o.gif

    But I think the blast of outward particles overlaying the dust is quite a good look actually. I lost the explosion that the shell originally had as from what I've seen on Liveleak Claymore explosions doesn't have any place.

    You can definately see a flash of flame as the claymore blows in videos, as for the smoke particles... Wouldn't it be possible to create an initial expanding smoke effect with a very short duration and as it is expanding place the static smoke in there? So you get the illusion of billowing smoke?

  21. Posted

    I don't want to over clutter the screen of normal users just so mission editors can sight them in perfectly, though you have a good idea. When I release it I'll include an optional scripts/peep_sight.sqf drop-in replacement that hints.

    I'm unclear as to what you mean by claymore layer, as for tripwiring doors, sure it's possible and it's the way I'd want to do it anyway.

    Put the claymore off to one side of the door and run the tripwire to the other, if you put the claymore in the middle of the room and the tripwire to it's front rotated 90 degrees across the doorway it'd be obvious you don't want to walk in there as there's a claymore looking at you.

    You mentioned 3 point system, the way I had it wasn't actually a three point system there's only a trigger going between the two points you specify, nothing coming from the claymore to the first point. I suppose I could implement that and I'd be slighly happier with it, I actually really like the ease of use of only having to specify one point though. Idunno, I'll have a think about it.

  22. Posted

    Okay, I've lowered the number of shrapnel bits to 400, still more than before and upped the damage of each bearing a tiny bit to compensate. This should help out you guys with slower computers. The damage that the shrapnel does is just a guess from what I've read, if anyone here knows it should do more or less damage please let me know. Basically I aim for near 100% dead at 30 meters and from a quarter to a bit over half of the enemy dead at 50, most others being injured.

    I've also included two scripts to allow mission designers to place already initialized claymores in missions and create thier own triggers for them, from simple tripwires/proximity trigggers to having the enemies intelligently blow claymores around thier perimiter when they spot you. Players can fully interact with these claymores placed by the mission editor disarming them, even turning them around. You can set the position, pitch and direction with the scripts so we can even hang them from trees.

    Here's how to use them, let me know if it's intuitive enough for you all.

    Easy way to get started:

    1. Place a claymore ammo box (always do this or claymores won't work!wink_o.gif.

    2. Create an empty helipad or any object you want to be able to place easily.

    3. In the init field of the empty helipad make a call to the included script: x = [position this, 40, -2, "claymore_1"] execVM "claymore\scripts\manual_initialize.sqf". Note, first argument is position, second argument is direction in degrees, third argument is pitch (negative numbers denote pitch up) and the final argument is the name of the public variable you want the script to assign your new claymore to.

    4. Create a trigger, activation code being: x = [claymore_1] execVM "\claymore\scripts\manual_detonate.sqf"

    That's it, do you guys think it's easy enough?

    So, I'm going to release them as this version most likely I just want to make sure there's nothing outstanding. Did anyone have any desperate last problems?

    I undestand there's still unrest about the new tripwire system, if many more of you have a whinge or even better provide me with good points why you can't use the newer realistic tripwire system for whatever it is you want to do I may consider putting it back. I'm pretty deadset on it though as I don't think you can set up a tripwire in such a fashion in a short amount of time (It's a short enough time as is but who wants realism when it involves waiting?). Plus, those tripwires were sort of suspended in space with nothing leading back to the claymore which is rather shit.

    edit: Forgot to actually post the new claymores, here.

    http://rapidshare.com/files/93464141/claymore.pbo.html

    edit2: Just saw your post dmarkwick, is multiplayer going to be possible? What's involved? As for the effects, looks great. I actually thought it looked more realistic as you had it before (with the custom explosion textures). It was just a bit jarring as you had the explosion then smoke suddenly appearing.

  24. Posted

    Can you please turn your graphics down to make sure it's not a graphics issue? I'm thinking it might just be the fact that you're rendering the effects from close up.

    So there's definately less delay with the fragments turned down?

    I'll see if I can make the individual pieces of shrapnel stay alive for sorter periods so they don't need to be calculated as long.

    Edit: Can you go to your config.cpp please and try this?

    class B_BallBearing : BulletBase {

    hit = 4

    indirectHit = 0;

    indirectHitRange = 0;

    visibleFire = 0.07;

    audibleFire = 0.07;

    visibleFireTime = 2;

    typicalSpeed = 1100;

    timeToLive=1;

    }

    Not the timeToLive, should allow the round to travel a good 800-1000 meters then stop simulating. Let me know if any of those things make a difference.

    I personally only have a tiny FPS drop and a very slight delay which I attribute to creating all the shrapnel. I could create the shrapnel over a larger amount of time but that'd sound and look weird.

×