erazeri / ccip Goto Github PK

Check compatibility for 1.40 changes:

-Added: Weapon muzzle velocities are now correctly defined per weapon and not per magazine as before (backward compatibility is maintained as magazine initSpeed is now considered when there is no initSpeed defined in the weapon, while a weapon defined initSpeed overrides the magazine defined value)

-Modified: InitSpeed in weapons - zero value in weaponType::initSpeed means that magazineType::initSpeed will be used (initSpeed set to positive values in a weapon means a constant speed of the weapon independent on its magazine. Negative values mean a multiplier for initSpeed set in the magazine. Setting it to 0 means that the speed is going to be taken from magazine, this equals to setting initSpeed in the weapon to -1)

This picture is a good demonstration:
http://pilvigalleria.dy.fi/imgs/arma3%202014-12-07%2000-42-01-855.jpg
You can see the debug line, the crosshair is where the impact is calculated to be and the yellow sphere is CCIP_impactPos with ATL Z at 0.
I`m asking for help to make it more accurate.
This was also the case with the original script:
https://github.com/jonimake/arma-ccip/issues

• A-10A
• SU-25SM

I have found out that your key is not compatible with mine from JNS Skycranes. The conflict is apparently caused by BIS' bug, as reported here: http://feedback.arma3.com/view.php?id=22133

Renaming either mine or your key fixes the 'conflict', but when trying to make the same key you have with name CCIP_v0.3a in Arma 3 Tools it doesn't let me type a dot, so that leads me to some sort of conclusion that your key was made by some older tool that (from what I read on BIS forums) is no longer supported and may cause issues.

Renaming your key to CCIP_v03a worked but renaming it to either CCIP_v0_3a or CCIP_v0-3a didn't work. Apparently using dashes/underscores causes conflicts... I have no idea why or how and apparently BIS doesn't either.

Now, I would rename my key from JNS Skycranes, but since I see that dots are not supported at all in the Arma 3 Tools, I would say it's better if it's handled on your side and renamed to CCIP_v03a or similar that would work (feel free to send it to me to test before releasing), there might also be issues with other mods but I haven't encountered them yet.
After some more testing I found out even weirder conflicts with my key, you can read about it in my comment on linked issue above. I would still suggest making a new key without the dot though, since it's not supported by Arma 3 Tools it probably shouldn't be used, but that's just my assumption.