I tested the issue under 1.64 RC and it is still broken there.
Aug 30 2016
Aug 29 2016
Aug 28 2016
Jul 12 2016
Please note magazineGroup config attribute is documented in https://community.bistudio.com/wiki/Arma_3_Weapon_Config_Guidelines - as such I believe this issue should be given more attention. Lack of common magazine interface is rather serious limitation of 3rd party mods.
May 10 2016
I would be surprised if dynamic lights were cast even during daytime before, when we could use that option regardless of time of day.
Removing action menu show condition is not the same as disabling feature completely. It was working correctly before.
This was designed to be so.
Implemented gun convergence 400 meters away for Wildcat and Pawnee
Data lock :/
Data lock is not yet over
Resolved locally, will be out after data lock.
I have some changes that should deal with it prepared locally, will have to wait some time though.
Increasing inertia to defeat the described effect.
For all I care it has been fixed long ago by pettka and programmers.
Unfortunately I believe the additional MG is not possible either. However will see about the rest during the course of next months.
The optics won't change I'm afraid. However something more could be done with other details, will consult it.
However, yeah, it could be improved,
It's proper damage texture for armored vehicles.
Should be working
Note that I added hidden selections. The "issue" with plates present in only some vehicles is a feature, not bug.
For all I care it should be present on DEV branch. On STABLE - when the patch is rolled out.
Problem was missing rotor center memory point. Should be up on DEV since yesterday.
Tracks should not sink into ground. Check out single player to see how it should look.
I think I resolved the issue already, so no misunderstanding on my part occured.
One zero was missing.
Fixed in next DEV update of Armor_F_Gamma
Fixed, added mirrors (being tweaked by modeler)
A placeholder solution for it is missionmaker should be able to simply disable AI for now.
That was message to programmer :)
Please think of solution for when flight time exceeds bullet lifetime in your free time. :)
Please try again.
Some feedback regarding APCs and AA vehicles:
- hitpoints and fire geometry AA vehicles will be improved.
- RCWS is delicate is by design. You're hitting an area where sensors/mechanics are stored, not just random place.
- Gorgon and Kamysh - you've just destroyed optics, so it's not surprise you can't aim anymore.
- AMV you managed to hit turret ring which is NOT armored well. Nice one.
- T-100 can indeed have smaller fragile zone around engine.
- There are few tanks in the world that can sustain APFSDS hit from THAT close. If anything, tanks should be more fragile to such powerful round.
- 10:07 You have managed to hit gun's mantle. What I would expect IRL is that you'd tear that turret apart, and kill all occupants of the turret.
Best regards, thanks for detailed report and hope you enjoy our game.
Considering as fixed unless proved otherwise
Please try if issue persists after next Dev branch update of armor_f_gamma
The issue is quite difficult to track because of way damage system works - primarily the lack of projectile and armour fragmentation causes it to be extremely difficult to balance.
Regardless, I'll try to fix such issues within available technology.
Chops, maybe you could check how's the situation now? Since 1.12 it should be much more difficult to get stuck with armored vehicles; not the best solution possible without deep changes in PhysX implementation, but at least one doesn't have to be that careful.
Could you provide more specific info, about what is working and what is not?
We have direction stabilization. The muzzle keeps direction compared to world coordinates.
Quite much like what I described in my tank tutorial under DAMAGE section.
Thanks for input :)
If I want to have damageable optics, I need to have way to make AI blind.
If I want blowoff panels and ammo storages, I need to remove rounds that have been blown up.
Without dedicated programming support and no scripts allowed in first place these are impossible. That's how the things are unfortunately.
PhysX bugs belong to PhysX master :)
Should be fixed in current dev branch
JohnnieConcrete, I believe you should take the point Gekkibi makes.
The compass must be centered, because its readings are tied to direction of camera. If you require it changed so much, please convince mod makers to create 3rd party mod as it is possible to alter look and position of compass this way.
Shoot first, ask questions later approach isn't working out well in this situation. If I wanted AI to fire at empty camo net, I would have placed invisible target for it to shoot at.
Of course, we can always take in account that tents, sandbags and camo nets can return fire, but personally I wouldn't expect them to do so.
The problem is that AI does not want to engage targets until discovered by enemy.
Only typing "veh reveal this" into units init (veh = target) makes AI start engaging the target - choose proper weapons, etc.
Desired effect is - after some time AI should engage target and return to hidden position.
Fixed in internal files.
If you insist on using setHit, you should use "main_turret_hit" or "vez".
Otherwise I advice you to use setHitPointDamage.
Should be improved by 23.09.2013. Changing shell type in 120mm cannon will now take as much time as reloading the gun; we should take cumbersomeness of action menu in account as opposed to yelling "MPAT"; can't track "unloading" the loaded shell at the moment.
Will be fixed soon
Thanks for detailed info in this excellent report. There has been problem with merge of localization files. Most of the errors that occured have been fixed since, but not all.
Fixed in dev branch
I'll try to do some magic on it but don't expect too much wonders.
Will be available on DEV soon
Fixed at least in current dev branch.
Generally fixed for all armoured vehicles. I'll only fix reported detail problems since now.
Helicopters are not my area of work... at least in A3.
Some issues will be improved soon-ish.
The improvement on APC damage handling is still pending.
I'll work on turret damage handling during course of October.
A HitHull class in HitPoints offers such feature - when it reaches > 0.9, the tank "catches fire" and explodes or burns a while later.
So, yes, there is still big room for improvements in that matter. ;)
We worked hard to make the penetration in A3 as good as possible. However there are technical limitations for simulation of penetration we have; currently the engine does not feature disintegration of projectiles after penetration, as it should occur with SABOTs; this is probably the reason for issues described.
- all armored vehicles in A3 have weak points: zones like engine, ammo compartments, turret mechanisms, crew members receive damage from explosions and penetrating shots, both as a "hitpoint" and for whole vehicle.
- the BTR-K is lightly armored vehicle, it's armor is mostly comparable with wheeled APCs we have ingame. I would expect the 120mm SABOT under normal conditions to pierce two 30mm RHA plates with ease.
For now the workaround would be to use round's velocity vector instead and push it through BIS_fnc_magnitude function to obtain numerical value.
Should be fixed with next update.
Isn't there one already?
Fixed by pettka long ago.
I'm checking what is possible to be done.
looking for feedback
I never said that.
All APCs received improved armor modelling.
Please note Kamysh armor is as weak as one on AMV, while Panther is generally very hard to penetrate with anything available in game. There is no EFP simulation yet.
Will be up soon
Quite important issue.
Another fast repro:
- Enter debug console.
- Track variables:
I reckon this is severe scripting issue. Assignment for Programmers in general.
I've applied the drag for APDS and SLAP rounds config. It's invaluable, thanks!
However this source:
States the .408 has really low BC. I tried to match the air friction so bullet shot with init speed of 930 m/s keeps supersonic up to 2200 meters.
Going to review .408 once again. Thanks for input!
Cannot reproduce. Rockets and missiles fall down after they lose speed.
You should use time instead of diag_tickTime, and try handle division by zero errors ;) otherwise your speed won't be exact to ingame speed
Please note my post was about 6.5mm ballistics, it's as accurate as it should be.
Haven't noticed the topic changed from its original name meanwhile, but anyway I wasn't talking about sight picture. Sorry if you got me wrong, English isn't my mother tongue :)
For your honesty I did some calculations about 6.5mm Grendel using avaiable sources online - ballistic tables.
Some maths regarding what you can observe in optics:
- drop at 300 yards: 5.10 MOA compared to 100 yards zero
- drop at 200 yards: 2.01 MOA compared to 100 yards zero
Representation in angle:
5.10 MOA is 0.085 degree - that's the difference between 100 and 300 yards.
2.01 MOA is 0.0335 degree - that's the difference between 100 and 200 yards.
Vertical Field of View of ARCO optics: 6.507 degrees
Let's say our screen resolution is 1680x1050. 1050 * (0.085/6.507) = ~ 14 px
Now please do following:
Place yourself as NATO marksman (with optics).
Fire 25 rounds out of your 30 round mag while in ARCO optics.
Then, use pause menu console and type setAccTime 0.1, execute.
What you observe is tracer flying 10+ pixels above center of reticle, at least on my screen it does so. Proven that, your claim about non-working ballistics isn't valid.
Best regards :)
NLAW/MBT LAW... let's see some RL data I've collected so far:
- Its top speed is said to be 275 m/s. Russian ATGMs up to AT-5 were slower.
- It self destructs after 5.6 seconds / 1000 meters.
- It reaches 400 meters under 2 seconds.
Other physical properties are mystery.
All is matter of scale :) Arma terrains are large and FoV settings are made so terrain features "feel" closer than they are.
The video is great but I'd rather see ballistics tables like this:
I did some more calcs. All are approximates of course, but shouldn't be worse than reality as I'm simply connecting the dots.
Time at 300 yards: ~ 0.4 seconds
Speed at 300 yards: ~ 433 m/s
Speed at 500 yards: ~ 295 m/s
Average speed: ~ 364 m/s
200 y = 182.88 m
182.88 m / 364 m/s = ~ 0.5 s (very roughly)
Added 0.4 TTF to 300 yards, it turns out that if your rifle features small muzzle velocity you should be satisfied with 0.9s time to flight to 500 yards. However if you shoot same round with longer barrel, it will reach target faster.
Remember weapon I refer to has a bit shorter barrel, the muzzle velocity is 883 m/s, not 1000 m/s!