VTB display size

[Golo]

Interesting , if its really a LUA change, i hope they can make a setting for this so we can choose.

 

Yes I think this should be standart practice.

If you do something that does not match RL model, (like this VTB display or in MiG-21 ASP missile and bombing piper simplifications) there should be an option to change it to LR specifications or tutorial how to do it via LUA or whatever for those who want it.

[OnlyforDCS]

 

I think that the symbols in the RWR are too large and will make them a bit smaller, but my worry is the numbers identifying the radars. I feel that they are as small as they can be and still being able to be readable.

 

 

Why would you do that? They are horribly difficult to make out anyway because they are so bunched up near the center of the display? Wouldn't the easier solution be to place them a little bit further from the center of the RWR? Currently the RWR is next to useless.

[Johnny Dioxin]

I've read every post carefully and decided to compare Zeus' approach to another example. However I don't see how your post reasonably contributes to the discussion.

 

But bashing people's posts does?

 

Good luck with that. Especially when they were not wrong. Anyway - react how you like, my participation in this thread is finished. You can call a cat a fish...

[Pikey]

Hold on a sec guys, the visibility question for those without TrackIR or similar products is rendered moot by way of ED's existing method of snap views.

 

Thus there's some merit in the argument on geting that 5mm trim around the VTB back again :)

[Manuel_108]

If you do something that does not match RL model, (like this VTB display or in MiG-21 ASP missile and bombing piper simplifications) there should be an option to change it to LR specifications or tutorial how to do it via LUA or whatever for those who want it.

 

That sounds like the best deal.

[sedenion]

Are you all aware that you args about a "0.5cm" or "1cm" margin of a "display" between a real or a virtual screen ?...

 

i created this topic for readability purposes (i don't care the real margin of the real Mirage 2000 VTB, and i won't use any ruler to calculate the real one in a millimeter basis, this is a non-sens !)... If i had not created this topic, who cared now about this display margin / size ?.... But since i mentioned this vtb display size, it now become a matter of life or death about the "realism"... and NO ONE to only point that : bigger is more readble... no, the fundamental question still the "realism"... And thanks god, the "real one" is bigger, so i'm very lucky, i don't have to argue with "realism enthusiasts" (euphemistic term) to plead my cause, they all want it "bigger" because the "real one is bigger"...maybe we prevented a nuclear war here...

 

The only real and pertinent question here is: Is the current "1.5cm" margin better or worst for a good readability... whather the real "0.5cm" or "1cm" of the real cathodic VTB screen of the Mirage 2000...

 

=> Razbam say: This is for people which don't have Track-IR, to allow keeping a good visibility without acting the "CTRL+SHIFT+NP2" combo... This is a good intension, but:

 

A: The fact is tha we usualy use the "Numpad 0" shortkey for "Panel View", which can be configured with specific head position to allow a good view to the VTB

 

B: By enlarging the VTB display, we can little enlarge some fonts, and have more amplitudes for the TDC, so a better readibily and ergonomy to read and select targets.

Edited January 21, 2016 by sedenion

[PiedDroit]

The Razbam's point makes sens. When it's not a blasphemy to cheat on pure reality to make things more readable or more ergonomic is a good thing, while you keep a balance between realism and ergonomy...

 

But in this precise case, i think the "numpad 0" key is here precisely to help user to have a good quick view to the panel... so, i think we can enlarge the VTB display to have in fact, a better lisibility...

I'd prefer a less protruding hud console instead of smaller VTB screen ;)

This would have the added benefit to make AoA and G indicators visible too (see that other thread on the subject)

Edited January 21, 2016 by PiedDroit

[sedenion]

Anyway... i have tested some tweaking LUA... we can enlarge the VTB display (optimizes the elements's position in the screen in fact), but it is mainly "hard coding" basis, since every elements is created separately with its own relative size and position...

 

I'am currently trying to do some mod with some care (this is not easy, and it's a "try and error" game)... However, i don't know if the target positions and TDC amplitude can be tweaked through LUA, so, this would be more comsmetic for now... TDC and targets remains in the "center"...

[Sarge55]

I'd prefer a less protruding hud console instead of smaller VTB screen ;)

This would have the added benefit to make AoA and G indicators visible too (see that other thread on the subject)

 

This ^^ absolutely. :thumbup:

[Peter5on]

So much whining... Just make it as an option, in special setting which we have for every aircraft.

 

1) For people that dont use track ir (bigger HUD,RWR symbols,radar, switches make everything bigger even make stick bigger) :)

 

2) For those who seek realism and own track ir.

 

Simple as that.

Edited January 21, 2016 by Peter5on

[Eagle0110]

Yes, such implementation make sense to a specific group of people, but for the rest of us there should be an option to choose...

 

Sent from my SM-N9002 using Tapatalk

Edited January 21, 2016 by Eagle0110

[sedenion]

WELL... i finaly made some tweaks on the VTB... I have no changed much things, i only have more used the available space, specialy at left and right. In fact, the VTB space is already tight at up and down... no very possible to do better than original...

 

However, i have resized some (not very usefull) texts, the heading scale, moved some elements, and i removed the floating points of the TDC's azimuth and range coordinates (since in the real one, it seem there is no floating points, and these floating points are 1) useless 2) anoying )

 

Fix list:

 

EDIT : See here: http://forums.eagle.ru/showthread.php?t=159313

Edited January 23, 2016 by sedenion

[T_A]

Looks much better , thanks sedenion.

[sedenion]

note: i think i have destroyed a recent fix... since i have made the backup from the 1.5 version, the target altitude is displayed in meter, and i remeber that in the new version, the altitude is displayed in feets... however i don't know where to fix this subtility, i will see tomorrow...

 

PS: Well, in fact, NO, at the top of the VTB, in PID mode the target altitude is in feet, but in PIC mode, it is in meter, this is "built-in"... i don't know if it is normal ( in guess this is bug however )

Edited January 22, 2016 by sedenion

[sedenion]

Ok, i made some last little fixes... file updated and fix list added... http://forums.eagle.ru/showpost.php?p=2652099&postcount=37

[Sarge55]

Very nice work sedenion. Is it possible to keep the range and azimuth numbers the old font size? No decimals is a great improvement but the font is a bit too small.

[sedenion]

Very nice work sedenion. Is it possible to keep the range and azimuth numbers the old font size? No decimals is a great improvement but the font is a bit too small.

 

Ho, nothing is impossibru... open the VTB_page_0.lua, at the line 274 and 286, changes the "{0.003,0.003}" to "{0.004,0.004}" (0.004 is the original size, hem... i don't commented the original here: BAAAAD...)

 

the famous lines in bold and underlined here:

 

local rdr_TDC_rng            = CreateElement "ceStringPoly"
rdr_TDC_rng.name            = "rdr_TDC_rng"
rdr_TDC_rng.material        = vtb_indication_font
rdr_TDC_rng.init_pos        = {0.15, 0.07, 0.0}
rdr_TDC_rng.alignment        = "RightCenter"
rdr_TDC_rng.formats            = {"%1.0f"} -- {"%1.2f"} 
[u][b]rdr_TDC_rng.stringdefs        = {0.003,0.003} -- => [/b][b]{0.004,0.004}[/b][/u]
rdr_TDC_rng.controllers        = {{"rdr_TDC_rng"}}
rdr_TDC_rng.parent_element    = vtb_rdr_TDC.name
rdr_TDC_rng.additive_alpha    = true
Add_VTB_Element(rdr_TDC_rng)

local rdr_TDC_azm            = CreateElement "ceStringPoly"
rdr_TDC_azm.name            = "rdr_TDC_azm"
rdr_TDC_azm.material        = vtb_indication_font
rdr_TDC_azm.init_pos        = {0.15, -0.07, 0.0}
rdr_TDC_azm.alignment        = "RightCenter"
rdr_TDC_azm.formats            = {"%1.0f"}  -- {"%1.2f"} 
[u][b]rdr_TDC_azm.stringdefs        = {0.003,0.003}[/b][b] -- => [/b][b]{0.004,0.004}[/b][/u]
rdr_TDC_azm.controllers        = {{"rdr_TDC_azm"}}
rdr_TDC_azm.parent_element    = vtb_rdr_TDC.name
rdr_TDC_azm.additive_alpha    = true
Add_VTB_Element(rdr_TDC_azm)

[Manuel_108]

Nice job sedenion! Already send your application letter to Razbam?

[Rlaxoxo]

Ho, nothing is impossibru... open the VTB_page_0.lua, at the line 274 and 286, changes the "{0.003,0.003}" to "{0.004,0.004}" (0.004 is the original size, hem... i don't commented the original here: BAAAAD...)

 

the famous lines in bold and underlined here:

 

local rdr_TDC_rng            = CreateElement "ceStringPoly"
rdr_TDC_rng.name            = "rdr_TDC_rng"
rdr_TDC_rng.material        = vtb_indication_font
rdr_TDC_rng.init_pos        = {0.15, 0.07, 0.0}
rdr_TDC_rng.alignment        = "RightCenter"
rdr_TDC_rng.formats            = {"%1.0f"} -- {"%1.2f"} 
[u][b]rdr_TDC_rng.stringdefs        = {0.003,0.003} -- => [/b][b]{0.004,0.004}[/b][/u]
rdr_TDC_rng.controllers        = {{"rdr_TDC_rng"}}
rdr_TDC_rng.parent_element    = vtb_rdr_TDC.name
rdr_TDC_rng.additive_alpha    = true
Add_VTB_Element(rdr_TDC_rng)

local rdr_TDC_azm            = CreateElement "ceStringPoly"
rdr_TDC_azm.name            = "rdr_TDC_azm"
rdr_TDC_azm.material        = vtb_indication_font
rdr_TDC_azm.init_pos        = {0.15, -0.07, 0.0}
rdr_TDC_azm.alignment        = "RightCenter"
rdr_TDC_azm.formats            = {"%1.0f"}  -- {"%1.2f"} 
[u][b]rdr_TDC_azm.stringdefs        = {0.003,0.003}[/b][b] -- => [/b][b]{0.004,0.004}[/b][/u]
rdr_TDC_azm.controllers        = {{"rdr_TDC_azm"}}
rdr_TDC_azm.parent_element    = vtb_rdr_TDC.name
rdr_TDC_azm.additive_alpha    = true
Add_VTB_Element(rdr_TDC_azm)

 

Is there a way to fix the misaligned radar screen when you switch the radar scan zones?

 

Example:

[ame=https://www.youtube.com/watch?v=Gj894hgF7HU]https://www.youtube.com/watch?v=Gj894hgF7HU[/ame]

[sedenion]

Is there a way to fix the misaligned radar screen when you switch the radar scan zones?

 

Example:

https://www.youtube.com/watch?v=Gj894hgF7HU

 

I don't have investigated... i will look at this, but, i believe the grid symbology is hard coded...

[sedenion]

Found and solved (see the "v2") : http://forums.eagle.ru/showpost.php?p=2652099&postcount=37

 

It was a problem of textures... original textures are not well aligned. For the B-Scope mode, Razbam have corrected the problem by adjusting texture square corrdinates, but not for the PPI grid...

 

Now (in my tweak v2): Textures are fully aligned, no need to adjust coordinates in LUA (Razbam if you read us... aligned textures are availables... )

[Rlaxoxo]

Found and solved (see the "v2") : http://forums.eagle.ru/showpost.php?p=2652099&postcount=37

 

It was a problem of textures... original textures are not well aligned. For the B-Scope mode, Razbam have corrected the problem by adjusting texture square corrdinates, but not for the PPI grid...

 

Now (in my tweak v2): Textures are fully aligned, no need to adjust coordinates in LUA (Razbam if you read us... aligned textures are availables... )

 

We should get payed I think ^^

[sedenion]

We should get payed I think ^^

 

Well... I am used to volunteer debugging, coding and reprair :D...

 

[ame]

[/ame]

[Sarge55]

Ho, nothing is impossibru... open the VTB_page_0.lua, at the line 274 and 286, changes the "{0.003,0.003}" to "{0.004,0.004}" (0.004 is the original size, hem... i don't commented the original here: BAAAAD...)

 

the famous lines in bold and underlined here:

 

local rdr_TDC_rng            = CreateElement "ceStringPoly"
rdr_TDC_rng.name            = "rdr_TDC_rng"
rdr_TDC_rng.material        = vtb_indication_font
rdr_TDC_rng.init_pos        = {0.15, 0.07, 0.0}
rdr_TDC_rng.alignment        = "RightCenter"
rdr_TDC_rng.formats            = {"%1.0f"} -- {"%1.2f"} 
[u][b]rdr_TDC_rng.stringdefs        = {0.003,0.003} -- => [/b][b]{0.004,0.004}[/b][/u]
rdr_TDC_rng.controllers        = {{"rdr_TDC_rng"}}
rdr_TDC_rng.parent_element    = vtb_rdr_TDC.name
rdr_TDC_rng.additive_alpha    = true
Add_VTB_Element(rdr_TDC_rng)

local rdr_TDC_azm            = CreateElement "ceStringPoly"
rdr_TDC_azm.name            = "rdr_TDC_azm"
rdr_TDC_azm.material        = vtb_indication_font
rdr_TDC_azm.init_pos        = {0.15, -0.07, 0.0}
rdr_TDC_azm.alignment        = "RightCenter"
rdr_TDC_azm.formats            = {"%1.0f"}  -- {"%1.2f"} 
[u][b]rdr_TDC_azm.stringdefs        = {0.003,0.003}[/b][b] -- => [/b][b]{0.004,0.004}[/b][/u]
rdr_TDC_azm.controllers        = {{"rdr_TDC_azm"}}
rdr_TDC_azm.parent_element    = vtb_rdr_TDC.name
rdr_TDC_azm.additive_alpha    = true
Add_VTB_Element(rdr_TDC_azm)

 

Sweet, thanks for providing that. You're working magic... :thumbup:

[sedenion]

today i will rework on VTB to make it more close to the real one http://rafalefan.e-monsite.com/medias/images/2000c.jpg

 

Specially, make the TDC and ADI smaller, and maybe some other symbologies... in the real one we can see that we have more clear space to view targets, it is less confusing...