Jets - Custom Panels (GPS, Camera feeds, ...)

[SLP 5]

On 9.1.2017 at 6:17 PM, oukej said:

Strange. I have it there. Can you please send me the actual vehicle and position (uav or turret control)?

Sorry, my mistake. Everything is working.

[oukej 2910]

You're not using Dev-Branch :) Main-Branch (default installation) is still month(s) away from getting some of this new stuff.

Once on Dev-Branch you can also check the first post and other pinned threads to learn more about what surprises there might be.

[oukej 2910]

 

On 5. 1. 2017 at 4:31 PM, bis_iceman said:

05-01-2017 

• Fixed: Default displays of vehicles without radar were incorrect

In compatibility/legacy mode, when the vehicle doesn't have a Custom Info component defined, the default is chosen according to radarType property. If there used to be a radar previously the default will include Sensors Display. The fix has been that radarType = 8 (compass) default no longer includes Sensor display

 

On 10. 1. 2017 at 6:39 PM, bis_iceman said:

10-01-2017 
EXE rev. 139925 (game) 

• Tweaked: The GPS is now oriented according to the camera's direction (WIP)

On 11. 1. 2017 at 7:03 PM, bis_iceman said:

11-01-2017 
EXE rev. 139940 (game) 

• Tweaked: GPS orientation is no longer affected by freelook 

21 hours ago, bis_iceman said:

12-01-2017 
EXE rev. 139954 (game)

• Added: Heading to the sensor display 

1 hour ago, bis_iceman said:

13-01-2017 
EXE rev. 139969 (game) 

• Added: A new  "mapOrientation" parameter (0 -  default North orientation, 1 - map is rotating with player vehicle's direction, 2 -  map rotates with weapon's direction) 
• Added: Heading, time and grid on the GPS screen

 

[Sniperwolf572 758]

4 hours ago, oukej said:

Tweaked: The GPS is now oriented according to the camera's direction (WIP)

 

I just want to ask, what is the motivation/reasoning behind this? The only thing that occurs to me is to make it harder to determine where North is without a compass, however, it's not a "magical minimap" kinda thing, it's a GPS, it's what it's supposed to do, you have 0-360 direction indicator anyway in the GPS header.

 

Are there plans to make this optional through client game options or is the mapOrientation parameter just so vehicles/equipment/controls can set it?

I find rotating GPS/minimaps very disorienting in games that implement it and I'd honestly rather keep the always north.

 

Additionally, rotating GPS still seems to have the rotating marker issue which makes markers useless on the GPS:

 

[lexx 1331]

Out of curiosity... with this system and being able to switch to a view of the gunner / driver positions of a tank, etc. would it also be possible to switch to the gunner UAV view if there is a UAV operator with a connected UAV in the group (not necessarily when the player is in a vehicle, but also on foot)? IMO, such a feature would make UAV operators a lot more valuable.

[ampersand38 344]

If the player connects to a UAV before opening a Drone camera custom info display, all that is shown is black.

However if the display is first opened, to show grey "NO CONNECTION", then the player connects to a UAV, the display functions as expected.

 

Steps:

Place UAV operator

Place drone

Start mission

Open UAV Terminal and connect to drone

Open drone camera displays

 

Otherwise it's really good!

 

[oukej 2910]

It seems that you're missing several other elements. Strange. What's your resolution and UI size?

Can you try resetting the layout preset to default, restarting the game and see if they pop back again?

Spoiler

 

[teabagginpeople 398]

7 hours ago, oukej said:

It seems that you're missing several other elements. Strange. What's your resolution and UI size?

Can you try resetting the layout preset to default, restarting the game and see if they pop back again?

  Reveal hidden contents

 

resetting the layout preset to default, restarting the game

 

just to note this worked. woops.  . thanks again.

[R3vo 2652]

Any chance for the CAM modules to also display the direction of the camera? I find the drone CAM kinda useless if one can't tell where it's pointing.

 

Other than that I really like the CAM display, only hope it also works smoothly in multiplayer =/

[dr. hladik 231]

14 hours ago, R3vo said:

Any chance for the CAM modules to also display the direction of the camera? I find the drone CAM kinda useless if one can't tell where it's pointing.

 

Other than that I really like the CAM display, only hope it also works smoothly in multiplayer =/

 

What exactly do you have in mind? Just heading?

[Strike_NOR 898]

Hey oukej!

 

I have just awoken from "the dead" in order to pitch some ideas and thoughts into the new Jets DLC. I have also written some coffee-break length material in the sensors thread that you may or may not find interesting :) .

 

I've always wondered: Since ARMA 2, you have had functional in-cockpit "3D" Head Up displays. They seem to be displaying on an "invisible" 3D Face/Pane floating in the cockpit, so when you turn your head around with Track IR, everything quickly get's unaligned with the game world. In example: If you are strafing tanks with the Wipeout, you may see green squares on the HUD, but they don't match with the actual position of the tanks in the game world, but, if you align the hud aiming reticule with the squares, you will actually hit the target!

 

This tells me that the in cockpit 3D-HUD display is rendered as a texture in the cockpit.

 

In ARMA 3 you introduced for the first time, proper red-dot sights with a "collimator" feature. This means that the sight always shows where the weapon is pointing. In an aircraft hud, you use the exact same technology, but the difference is that you can display a lot more information in an aircraft HUD. 

Well... Here's my question:

• Is it possible to introduce collimator sight technology to aircraft 3D cockpits?

 

Even if you don't make it a fully flight-simulator feature. It would still massively improve the current implementation, because sights would actually align with targets :)

 

Edited: Do I even ARMA 3? Just realized I was flying mod aircraft. My bad.

 

I'd like to know what you think about that :)

Edited February 7, 2017 by Strike_NOR
Not applicable

[goldenfiver 11]

I hope this wasn't asked before- can we get the GPS info displyed on the cockpit's MFD? (RHS has done this in one of their russian planes)

[CANADAVE 14]

I've been playing allot with main branch TGP , it I such huge improvement to aircraft- so thanks BIS!

 

Wondering if the next update will (or can) allow the TGP to provide a visual indicator of its current FOV / its current  AREA locked position to the pilot both on HUD and as a  top-down geo-location on the sensor display?

 

Being able to reference a pilot selected reference point on the ground (even if only visible when seen within HUD FOV) is important for heads-up orientation when flying, as well as CAS support of non-locked targets (Infantry clusters etc...).  Currently this can only be achieved by placing SHIFT-CLICK marker on the map and then aligning the TGP to the in-game icon (which gets disabled at some difficulties and does not deliver the true real-life functionality). 

 

Sorry if this is posted in the wrong area.

 

 

 

[pierremgi 4737]

My home-made GPS (MGI tactical pack) is also speed responsive (not only!) but, I added a on-the-fly zoom in/ zoom out with ctrl + scrolling in /out mouse. One of the most useful thing, IMHO.

[R3vo 2652]

Quote

 

Added: Heading for camera feeds 

 

 

Thanks, much appreciated!

[a_killer_wombat 120]

NOTE: Re-posting this from another thread since I think this is the more appropriate place for it.

 

I have two suggestions to help make the radar display more user friendly.

 

Firstly, at the moment the radar display includes 4 circles of different sizes which help signify different ranges. For example, Figure A shows the radar display at 12km resolution which means each circle indicates +3km range with the largest outer circle signifying 12km (12 / 4 = 3). This is really helpful for giving the player quick and easy ranging feedback for all the "objects" which the sensors detect. 

 

However, when the radar display resolution is toggled to 6km or 3km resolution (see Figures B & C), this ranging feedback is harder to understand due to the number of circles not adapting with the change in resolution so each circle indicates a non-round/non-absolute number of distance (for 3km resolution, each circle indicates +0.75km). 

 

I suggest that the number of circles displayed should adapt depending on resolution. For example, 6km resolution could have 3 circles instead of 4 where each circle indicates +2km range and 3km resolution could have 3 circles as well where each circle indicates +1km range. It's easier for players to estimate range when working with round/absolute numbers.

 

Secondly, the radar display already provides useful target information such as the target's altitude, speed and range (see Figure D). However, one very useful target info the radar display is missing is the target's bearing/azimuth in relation to the player's vehicle. I suggest that the radar display should also display this info in a similar manner as it displays altitude, speed and range.

 

From the player's point of view, knowing the bearing to a target is very important (I would argue it's more valuable info than target speed). For example, it allows an attack helo pilot to quickly and accurately notify his gunner/co-pilot where to look for a target ("Gunner, target vehicle bearing 187").

 

Figure A (radar at 12km resolution):                            Figure B (radar at 6km resolution):                                        Figure C (radar at 3km resolution):                                 Figure D:

                                                                                        

[x3kj 1247]

Loaded devbranch today - i get Left/Right panel actions even as a player. Also, they are priority it seems over most other stuff - not good.

 

Also, i tried the Buzzard and it seems that the impact point calculation seems to be innacurate. The bombs hit short in most cases (or if turning while dropping, they miss left/right). It feels as if the "drift" of the airplaine is not accounted for. In somewhat level flight at 500kph i had to use the bottom of the circle to somewhat hit near where i want.

[oukej 2910]

6 hours ago, oukej said:

This is not intended. Caused by data mismatch. Only one of those actions (Right panel) should be in the Action menu and that only if you don't have it bound to some input. It should be gone again with the next Dev-Branch update. (it can possibly reappear in the following days)

[oukej 2910]

On 10. 2. 2017 at 2:06 AM, a_killer_wombat said:

I suggest that the number of circles displayed should adapt depending on resolution.

 

Secondly, the radar display already provides useful target information such as the target's altitude, speed and range (see Figure D). However, one very useful target info the radar display is missing is the target's bearing/azimuth in relation to the player's vehicle. I suggest that the radar display should also display this info in a similar manner as it displays altitude, speed and range.

 

From the player's point of view, knowing the bearing to a target is very important (I would argue it's more valuable info than target speed). For example, it allows an attack helo pilot to quickly and accurately notify his gunner/co-pilot where to look for a target ("Gunner, target vehicle bearing 187").

This is no longer possible with display submodes. One could create separate displays for each range with different visuals. But we wanted to limit the amount of panels to a level where it can be still reasonably toggled only in one direction. So we created submodes but the submodes - unlike individual modes - use the same resource.
However we can at least adjust the ranges so that the circles represent a "nicer" number.

 

On 10. 2. 2017 at 2:06 AM, a_killer_wombat said:

However, one very useful target info the radar display is missing is the target's bearing/azimuth in relation to the player's vehicle. I suggest that the radar display should also display this info in a similar manner as it displays altitude, speed and range.

Not sure we can fit that in. There's already the bearing of own turret or vehicle shown in the title bar. Getting the target's bearing is often just a flick away. Otoh the operator has no other good way to get target's speed or altitude. Range can be estimated from the circles but you may want to have more precise info to select proper weapons. There's also target's own bearing which would be commonly displayed elsewhere but we thought the travel vector could be enough in this case.

[Callsign 128]

@oukej Thanks for all the info about all the changes to the jets - overall the change is a dramatic improvement and I'm really enjoying the added complexity - it makes flying much more satisfying.

I've noticed the recent change in pilot FOV (in the Wipeout at least) and I'm not really a fan since it restricts overall visibility in 1st person (I assume this was done in order to make the MFDs more clear to read).

Would a compromise be to put the same information from the MFDs in the new UI modules and restrict what is displayed back in the MFDs (given the constraints of render to texture)? Surely this would also allow for the removal of more of the game UI? It would also be nice to see at least some differences between Opfor/Blufor vehicle UI modules, even if only cosmetic.

Keep up the great work!

[xxgetbuck123 945]

12 hours ago, oukej said:

This is no longer possible with display submodes. One could create separate displays for each range with different visuals. But we wanted to limit the amount of panels to a level where it can be still reasonably toggled only in one direction. So we created submodes but the submodes - unlike individual modes - use the same resource.
However we can at least adjust the ranges so that the circles represent a "nicer" number.

 

@oukej If changing the radar range zoom on the display is not possible then what does this mean? 

class SensorDisplay
					{
						range[] = {10000,5000,3000};
					};

I took it as radar range sub modes? The '10000' is the 10km that the radar is default zoomed at with my aircraft, but '5000' 5km & '3000' 3km seem to have no effect. 

 

 

[x3kj 1247]

4 hours ago, Callsign said:

@oukej
I've noticed the recent change in pilot FOV (in the Wipeout at least) and I'm not really a fan since it restricts overall visibility in 1st person (I assume this was done in order to make the MFDs more clear to read).

Press Minus on Numpad two times quickly, problem solved.

[KoalaDSK 122]

55 minutes ago, x3kj said:

Press Minus on Numpad two times quickly, problem solved.

 
Or we will see some FoV (field of view) slider in the future and people could decide according to their display setup (4:3, 16:9, 16:10, 21:9, VR HMDs - just dreaming), how much they want to see on their screen edges. For now, pressing two times the Numpad Minus key is a dirty solution because everytime it changes to the default FoV if you get in/out a vehicle or static weapon.

[x3kj 1247]

4 minutes ago, KoalaDSK said:

 
Or we will see some FoV (field of view) slider in the future and people could decide according to their display setup (4:3, 16:9, 16:10, 21:9, VR HMDs - just dreaming), how much they want to see on their screen edges. For now, pressing two times the Numpad Minus key is a dirty solution because everytime it changes to the default FoV if you get in/out a vehicle or static weapon.

He was complaining about too small FOV due to removal of the silly "speed zoomout" mechanic. Not something that affects you in a static weapon and only marginally in a ground vehicle. What you are suggesting is more like general FOV adjustement.

Keep in mind that certain vehicles/ vehicle positions can have different FOV limits and default FOV and not without reason. So a "universal slider" could introduce more issues.

[KoalaDSK 122]

31 minutes ago, x3kj said:

He was complaining about too small FOV due to removal of the silly "speed zoomout" mechanic. Not something that affects you in a static weapon and only marginally in a ground vehicle. What you are suggesting is more like general FOV adjustement.

Keep in mind that certain vehicles/ vehicle positions can have different FOV limits and default FOV and not without reason. So a "universal slider" could introduce more issues.

That's definitely a point but we should not forget that we still have the zoom function (right mouse by default) if there are problems with the readability of the MFDs. But never mind, let's get back to the topic and maybe discuss the FoV topic in another thread.