yannikh / itc_air Goto Github PK

When you are using night vision and have an MFD with PiP open your visibility is reduced to a point where you have trouble making out your wingtips.

Night vision with MFD without PiP:

Night vision with MFD with PiP:

The error message has to do with the laser marker function which I've opened in another issue to keep things seperate.

Mods used: CBA, ACE and ITC AIR.

Laser Code Setup - Seeker & Sender

Have it toggled via CBA keybind.
Ideas:

• setVectorUp - simplest to implement, but ugliest
• change center of mass - shift it back and forth. Probably will look nicest, but be most prone to bugs. Will require vector magic.

In real thing semi-circle becomes longer or shorter based on pitch - https://youtu.be/-a3ZTkP76YI?t=664 . Overwrite default behavior or create a new control.

Add configuration options for multiple seat aircraft like attack helicopters, but also ground attack fighters.

I went through the functions and sqflint showed me the following errors:

_plane isn't a parameter in this file:

_weapon isn't parametrized:

_trackObject not defined in file:

_wpName not defined:

_wpName not defined:

JDAMs can currently fall short at 30 degrees and go long at 80 degrees. Guidance code needs to be revisited.

Activating the laser and entering night vision results in an error message and no laser being displayed.

Transcript of the error:

'...ct 0, _relEnd select 1, _end select 2];
|#|drawLine3d[_startPos, _endPos, [1,1,1,1]...'
Error Type Any, expected Number
File itc_air\functions\ui\drawLaserBundle.sqf
[itc_air_ui_fnc_draw_laser_bundle], line 10

Image of the error message:

I've opened the night vision glitch in another issue to keep things seperate.

Mods used: CBA, ACE and ITC AIR.

At first Rover camera was hovering somewhere on the water level, completely static, but it was connected, since I could see pilot changing view modes. Then we've changed jet and welp, I could watch the plane, but not the ground, the camera was reversed or rotated somehow :/ Previously we used A-10E (vanilla A-164) and now F-181E. We switched back to A-10E and the same thing was happening - I could watch A-10 flying from beneath.

Test various colours for the pitch indicator, user feedback suggested making the current pitch a different colour from the frame

Hi.
First thank you for this awesome mod.

I save some problems since last update.

• Now MicroDagr and mod looks unlinked. I put coordinates in the Microdagr but no WP are created. (was one of the best features in the mod).
• There are a lot of new keys to touch. Is possible to grant Joystick support for your mod? I have got thrustmaster MFDs and would be great not using the T.A.R.G.E.T with Arma 3.
• There are some bugs in ultrawide screens. (the left mfd goes out from the buttons frame).
  NOW IDEAS
  2nd monitor support for this mod? (like AThena )
  Radar sensors in the mfd

thanks

Enable IR laser to pulse

Allow pilots to change their rover codes.
In absence of dialog to do this, just a keybind to go up and down in freq would work.

Variables meant to be global are currently set through remotely executed scripts that set them. the setVariable command has this functionality built in through setVariable [var, val, public].

All local variables in files should use the private keyword if not declared through a params function or in a private-array.

The ALT/HDG mode seems to maintain ALT/HDG of when AP is initiated, but I wish if I could designate ALT/HDG to whatever value I like (simply think of commercial aircraft's AP). Setting HDG to a certain WP could be really great, too.

If needed, I could give some hand on that work

Simulate radio signals for the rover to establish connection. Look in to possibly using ACRE functionality to calculate signal strength.

#21 related.
Since for now many popular add-on aircrafts don't have compatibility (RHS, Firewill, ...), not having base compatibility for those aircrafts results in lack of usage of this addon overall. Although MAV or other features cannot be used in all cases, features like STAT and NAV could work in general.

So in order to encourage plane add-on devs to update to cocmpatibility, how about giving basic features I talked above and add an addon option to turn base compats turned on or off? Maybe leaving a meesage talking that the aircraft is using base features only on options page or anywhere.

Implement a more realistic radar for relevant planes. Raise the detection range(can go up to 50nm in real life) but lower the identification range, so the radar will recognise objects but won't tell you what they are other than ground vehicles or air vehicles.
Allow the TGP to slew to the current radar target.

Gripen radar settings:
FOV: 60/45
Range: 30000/30000
ID Range: 2000

add base classes and/or defines for itc_air TGP(pilotcamera) config based on one or more real life TGPs(litening AT, sniper XR, etc) and features config.

Allow players to look at the rover screen of another player.

No manual available anymore anywhere, all links (Steam and Armaholic) are dead.

Feel free to edit and add to this issue, here are my ideas how to improve the code:

• add functions headers
  • jdam
  • fuzing
  • datalink (rover broadcasting, possibly steerpoint sharing between aircraft)
  • rover (rover viewing, ideally both as handheld device and PiP monitors)
  • ir_laser
  • targeting
  • steerpoints
  • UI
• GVAR macro (consider adding component prefix, for example: itc_ap_mode, etc.)
• standarize debugging - use BI's function system or do it like cool kids from CBA