Jump to content

Recommended Posts

Posted

I found an option in the mission editor under the last tab on the airplane group options. It says Waypoint Bullseye and it goes from 0 to 20.

 

What is that exactly? I thought (and I think it should) the bullseye has to be taken from the mission editor bullseye itself rather than a waypoint in some special tab.

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted

It means the radar cross designator in the radar display is giving bearing and distance indications about a WP you set instead of the default bullseye in the map.

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted

i see those numbers change when you press one of the buttons to the right of the vtb, do you know that those are for?

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted

01-02-03.

 

Wp1-Wp2-Wp3

 

So, by default (00) the cross is giving data from the map bullseye. If you change this, to for example Wp1, the default data is giving from that WP1.

 

If you change manually inside the cockpit to 01-02-03, you are changing the reference WP for bearing and distance on the radar cross designator.

 

I think XDDDD

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted

Thats quite interesting.

 

But I flipped those VTB buttons on the right and the numbers did change, however I did not change the mission editor option (the one I posted this thread for). So I wonder why does that option even exist if I can change it in the VTB.

 

Could it be just to set a default? Like if I want to start the mission with all bearings and distances from X WPT but I still can modify it in game?

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted

I just did some testing. The 00 "point" is your own aircraft, the VTB does not recognize the bullseye as a 00 waypoint. But if you change the waypoint to one of your route's then it does recognize them.

 

Too bad, I kinda wanted the bulls to be recognized as it is a huge help.

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted

I think so.

 

The most useful thing is the bullseye. Every flight no matter his position, are going to give the BRAA using the bullseye, because is a common point. So changing to a WP as default in the editor doesnt make to much sense for me, but is an option.

 

In flight you know that in 00 you have the common bullseye for BRAA but if you need a WP as reference for something, you can change it and use this information.

 

But one thing. The WP reference is changed in the left side of the radar display, not the right side. Is the third switch from the bottom right.

 

EDIT: You are right, 00 is your own position, but as Robin said, is very easy, make your first WP to be over the bullseye and you have best of both worlds. Own reference. Bullseye reference and dinamyc WP reference if needed.

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted

Yes, on the left, im sorry my brains just inverted.

 

And yes, setting it to a waypoint works of course, just like in the f15. But I see all the systems working here in regards of INS, so Im wondering if we are doing something wrong. Perhaps in the PCN that you set it manually would work? Well in should pre load from the mission editor anyway if it worked, right?

 

I spent all day reading the manual and understanding every single piece of the bird. I even tested the electrical systems to see if they matched the manuals BUS Map :D

 

So im at the point of being very detailed now :book:

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted

The radar display reference is independent from your HSI or the PCN.

 

So you can set WP1 over the bullseye in the mission editor as default point and then in cockpit the 00 would be WP1-Bullseye and at the same time you can enter any WP on the PCN to fly at, but the radar display will remain with the 00 reference. No matter if you change the PCN WP.

 

The HSI, HUD and PCN will point you to the WP selected but the radar display will keep the 00 reference all the time.

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted
...So you can set WP1 over the bullseye in the mission editor as default point and then in cockpit the 00 would be WP1-Bullseye....

 

You meant 01 would be WP1-Bullseye, right? 00 is your own aircraft, always.

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted

Yes...00 Own position reference. 01 whatever you have in the editor.

 

XDDDD, I also have an inverted brain.....

 

Sorry for the confusion

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted

Okok, I started to think I hadn't understood anything from before :joystick:

 

Manual states the following:

 

The INS controls the information displayed in the following instruments:

 HUD: Aircraft heading, attitude and current waypoint navigation.

HDD: Aircraft heading, attitude and waypoint position, including bullseye.

 

So I thought they were not independant. Thoughts?

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted
Okok, I started to think I hadn't understood anything from before :joystick:

 

Manual states the following:

 

The INS controls the information displayed in the following instruments:

 HUD: Aircraft heading, attitude and current waypoint navigation.

HDD: Aircraft heading, attitude and waypoint position, including bullseye.

 

So I thought they were not independant. Thoughts?

 

Most of the information on you VTB is connected to your INS, what have you not understand ?

Helljumper - M2000C Guru

 

Helljumper's Youtube

https://www.youtube.com/channel/UCK3rTjezLUxPbWHvJJ3W2fA

Posted

Oh, so INS and PCN are two separate things?

 

Now I dont understand sorry

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted

Right! That's what I knew, but then I dont understand what you said about the VTB being independant from the PCN.

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted (edited)

The VTB radar cross reference is independent from the PCN-HUD-HSI. Not ALL THE DATA SHOWED ON THE VTB. I mean only the data on the radar cross designator, (reference point-bearing distance), the rest of the data in the VTB is LINKED to the PCN.

 

First Pic:

 

The WP1 is OVER the bullseye, adjusted in the mission editor as teh default VTB point (01). In this pic you can see i´m flying directly to the bullseye-VTB reference 01.

 

RzT9qiJ.jpg

 

Now look at the VTB. You can see my reference point 01, and the bearing to the bullseye-Wp1, 178 ( this is because i´m not perfectly aligned. ). The distance is related ata where i put the radar cross designator.

 

Now lok at the PCN. I´ve selected WP2 and the distance and bearing are represented in the PCN-HUD-HSI independently from the VTB reference 01.

 

WM4X4DY.jpg

 

TSOPAeA.jpg

 

Now i´m aligned with the WP2 as you can see in the HUD, HSI and PCN.

 

peqY07X.jpg

 

2aYB0fm.jpg

 

DM5fDzD.jpg

 

But the VTB still points to WP1-Bullseye on the new bearing, 232.

Edited by Esac_mirmidon

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted

Perfect!

 

Now... What about if you put the WP1 over the bullseye instead of using the option in the aircraft tab?

 

Does that work the exact same way?

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted

Is the same. In the first example it will be your default point. In the second you must use the VTB button to cycle over the desired WP

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted

But I dont think thats the way it works. You see, the tab option is just a virtual way to tell the aircraft that waypoint 1 (for example) is going to be your bullseye but in the mission editor the actual WP1 may not be over the mission bullseye. Thats why I doubted.

 

Sorry I could not test it now thats why I asked you to.

 

Thanks!

 

Is it normal that these PCN modes only show the second part of the description (after the slash)?

 

TR/VS Time remaining to waypoint/Ground Speed

D/RLT Distance / Bearing to waypoint or offset waypoint.

  • Like 1

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted

Ok no! Nevermind. The option tab is just to set the VTB as WP1 (for example), but the bullseye must be placed on a WP or the other way around.

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

Posted

You can see in my pics for example:

 

WP2 is showing in the PCN both Bearing and Distance to the WP.

 

Be sure you have BOTH DEST and PREP buttons with the same WP choosed. The same for Time to WP/Ground Speed. You must set both PREP and DEST with the same WP number. NOT 00 in PREP.

" You must think in russian.."

[sIGPIC][/sIGPIC]

 

Windows 7 Home Premium-Intel 2500K OC 4.6-SSD Samsung EVO 860- MSI GTX 1080 - 16G RAM - 1920x1080 27´

 

Hotas Rhino X-55-MFG Crosswind Rudder Pedals -Track IR 4

Posted

This question still stands.

 

Is it normal that these PCN modes only show the second part of the description (after the slash)?

 

TR/VS Time remaining to waypoint/Ground Speed

D/RLT Distance / Bearing to waypoint or offset waypoint.

 

So the first one only shows me GS and de second one just bearing.

Intel Core i5-8600k + Cooler Master Hyper 212 EVO | Gigabyte GTX 1070 Aorus 8G | 32GB DDR4 Corsair Vengance LPX Black 3200MHz | Gigabyte Z370 Aorus Gaming 3 | WD Black SN750 NVMe 500GB | Samsung 850 EVO 250GB | WD Green 240GB | WD Caviar Black 1TB SATA 3 | WD Caviar Blue 500GB SATA 3 | EVGA 650 GQ 80+ Gold | Samsung CF391 Curved 32" | Corsair 400C | Steelseries Arctis 5 --- Razer Kraken X Lite | Logitech G305 | Redragon Dyaus 2 K509 | Xbox 360 | Saitek X-52 Pro | Thrustmaster TWCS | TrackIR 5

  • Recently Browsing   0 members

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