Jump to content

Recommended Posts

Posted

Hi !

 

Selection of waypoint 00 on VTB set our aircraft as the bullseye position and bullseye infos are distance and azimut of the TDC from it. Ok I have no problem with that.

 

But if I select any other waypoint from the original flight plan or added in flight, the distance/azimut infos on the VTB look totally wrong and link to nothing coherent.

 

Exemple: the bullseye is 6nm in front of me bearing 212. I put my TDC at this position and bullseye infos show 371/296 ... :huh:

 

WIP ?

[sIGPIC][/sIGPIC]

 

Intel I7 8700K / RTX 3080 / 32Go DDR4 PC21300 G.Skill Ripjaws V / MSI Z370 Gaming Pro Carbon / Cooler Master Silent Pro Gold - 1000W / Noctua NH-D14 / Acer XB270HUDbmiprz 27" G-synch 144Hz / SSD Samsung 860EVO 250Go + 1To / Cooler Master HAF X / Warthog+VPC WarBRD / Thrustmaster TPR / Track-IR v5 + Track Clip Pro / Windows 11 64bits.

Posted

Same here, checked with a teammate too with similars results predefining it while editing mission like aircraft options or selecting it throught "N" switch.

Posted

The bullseye coordinates displayed on the VTB show the TDC position relative to the bullseye.

 

When bullseye is 0 (no bullseye) it shows the TDC position relative to the aircraft. When you have selected a waypoint as the bullseye, the coordinates will show the TDC position relative to the selected waypoint. I have not tested if the values are correct because I was busy with INS alignment and drift errors. But that is how it is supposed to operate.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Posted

Hi Zeus !

 

Yes I agree it should operate this way, but actualy only TDC position relative to aircraft is correct. TDC position from bullseye is wrong.

[sIGPIC][/sIGPIC]

 

Intel I7 8700K / RTX 3080 / 32Go DDR4 PC21300 G.Skill Ripjaws V / MSI Z370 Gaming Pro Carbon / Cooler Master Silent Pro Gold - 1000W / Noctua NH-D14 / Acer XB270HUDbmiprz 27" G-synch 144Hz / SSD Samsung 860EVO 250Go + 1To / Cooler Master HAF X / Warthog+VPC WarBRD / Thrustmaster TPR / Track-IR v5 + Track Clip Pro / Windows 11 64bits.

Posted
Hi Zeus !

 

Yes I agree it should operate this way, but actualy only TDC position relative to aircraft is correct. TDC position from bullseye is wrong.

 

That is the information that I have. I must guide myself from it. Remember that it doesn't matter how other aircrafts work. All of them are different even if they perform the same job.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Posted

Yes of course. I only report that the TDC position relative to bullseye actually give us wrong numbers:

 

Exemple: the bullseye is 6nm in front of me bearing 212. I put my TDC at this position and bullseye infos show 371/296

[sIGPIC][/sIGPIC]

 

Intel I7 8700K / RTX 3080 / 32Go DDR4 PC21300 G.Skill Ripjaws V / MSI Z370 Gaming Pro Carbon / Cooler Master Silent Pro Gold - 1000W / Noctua NH-D14 / Acer XB270HUDbmiprz 27" G-synch 144Hz / SSD Samsung 860EVO 250Go + 1To / Cooler Master HAF X / Warthog+VPC WarBRD / Thrustmaster TPR / Track-IR v5 + Track Clip Pro / Windows 11 64bits.

Posted

Same here, see link.

Hardware: Intel i5 4670K | Zalman NPS9900MAX | GeIL 16GB @1333MHz | Asrock Z97 Pro4 | Sapphire Radeon R9 380X Nitro | Samsung SSDs 840 series 120GB & 250 GB | Samsung HD204UI 2TB | be quiet! Pure Power 530W | Aerocool RS-9 Devil Red | Samsung SyncMaster SA350 24" + ASUS VE198S 19" | Saitek X52 | TrackIR 5 | Thrustmaster MFD Cougar | Speedlink Darksky LED | Razor Diamondback | Razor X-Mat Control | SoundBlaster Tactic 3D Rage ### Software: Windows 10 Pro 64Bit

[sIGPIC][/sIGPIC]

Posted

And Zeus' answer on that:

TDC/Bullseye relationship is untested and very likely buggy. I must finish some INS part before working on the bullseye/TDC relationship.

 

Let's be patient :)

spacer.png

  • 1 month later...
Posted

Up ! :P

 

Is it normal that azimut is given TO bullseye and not FROM ? I don't think so according to how it works in BMS's F-16 and AWACS reports, but maybe it's a french specificity ?

And same question for distance/azimut and not azimut/distance (as for F-16/awacs) ?

[sIGPIC][/sIGPIC]

 

Intel I7 8700K / RTX 3080 / 32Go DDR4 PC21300 G.Skill Ripjaws V / MSI Z370 Gaming Pro Carbon / Cooler Master Silent Pro Gold - 1000W / Noctua NH-D14 / Acer XB270HUDbmiprz 27" G-synch 144Hz / SSD Samsung 860EVO 250Go + 1To / Cooler Master HAF X / Warthog+VPC WarBRD / Thrustmaster TPR / Track-IR v5 + Track Clip Pro / Windows 11 64bits.

Posted
Up ! :P

 

Is it normal that azimut is given TO bullseye and not FROM ? I don't think so according to how it works in BMS's F-16 and AWACS reports, but maybe it's a french specificity ?

And same question for distance/azimut and not azimut/distance (as for F-16/awacs) ?

 

It reads range/ azimuth.

 

It's strange but it's like that in the real one.

 

Azimuth should be given "from" BE off course.

Mirage fanatic !

I7-7700K/ MSI RTX3080/ RAM 64 Go/ SSD / TM Hornet stick-Virpil WarBRD + Virpil CM3 Throttle + MFG Crosswind + Reverb G2.

Flickr gallery: https://www.flickr.com/gp/71068385@N02/728Hbi

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...