Jump to content

Recommended Posts

Posted

I don't think the avionics support it.

Motorola 68000 | 1 Mb | Debug port

"When performing a forced landing, fly the aircraft as far into the crash as possible." - Bob Hoover.

The JF-17 is not better than the F-16; it's different. It's how you fly that counts.

"An average aircraft with a skilled pilot, will out-perform the superior aircraft with an average pilot."

Posted

there's a few ways to go about it but i don't think you'll find them useful

 

- load the bullseye in the dtc as a markpoint/waypoint etc, then use the hsd or f10 map and a ruler etc

- same as above but drop a mark on the f10 map

- get an awacs up and ask for picture/bogey dope

 

you meant if there's some button that'll automatically create a bullseye reference for a bogey for you? The bullseye could be a 100 miles away i'd probably use the datalink and/or drop markpoints for local reference?

 

do you have an example of what you'd like to achieve?

Posted
do you have an example of what you'd like to achieve?

Don't know about the OP, but what I would like to achieve is to look at my HSI, radar, or even tgp (although reading it on some other slaved sensor probably helps avoid some of the screen clutter) and see a bulls readout for the current point I'm aiming at. If you've been in the Viper, Hornet, or Warthog, you will have seen this (and its being in the Viper makes it at least a bit logical that it would also be in the Jeff). It's not a button — just a bulls symbol that constantly sits in the corner and give me a reading of where I'm pointing at any given moment.

 

I can then communicate this position to other pilots, and they can slew over their sensor of choice to the same position and see if they see something. It's a bit like SPI transmission in the Hog, except without the need for data linking.

 

Conversely, when AWACS gives a general bulls call, I can just slew over my sensor to that point and see if I can pick anything up, or be ready to instantly lock up something that will appear there.

❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧

Posted

yeah i use the bullseye relative coords in the hornet as it's the only way to share locations at the moment

 

in the jf however you have a working datalink, so i just haven't felt the need for it to be honest

 

there's a thread with a question to the devs regarding if the jf provides 'shareable' spi's through the datalink - while we're waiting for an answer, a workaround i 'm using is either buddy lazing (i laze something / fellow pilot picks it up through lss) or good old discord voice comms :P (you can point your tgp somewhere, get the coords saved to a markpoint, relay the markpoint)

 

back to the point - regarding bullseye offsets, as far as i know there's no constant readouts of where your sensors are pointed at, in relation to the bullseye, however you can target weapons relative to it, the functionality seems to be in early access though/not fully fleshed out

 

the way to go about it is, drop a pp on the bullseye before mission starts, then whenever you get an offset (awacs, your mates etc) hit the oap in the ufc, enter your offset, hit oap again so that it's lit and.... that's where it's not working anymore :P navigation or slaving sensors in oap mode is not complete at the moment it seems. However, a few munitions will allow you to release in oap mode, so in theory you can make some use out of it (maybe :S)

Posted

ok, understood, to the best of my knowledge, you can't get target or own relative bra from the radar/hsi like with the hornet if you hit the a/a wp button like in my screenshot. You probably know about the ruler on the f10 map - that might be a workaround or eyeballing it the old school way like with other airplanes

 

the datalink in the hornet is kind of in the same state as with the jf17, in mixed flights you'll get mixed results - we only managed to get consistent views if everyone is in a jf-17, i recall a statement from the devs though that they're supposed to play nice with each other eventually, so hopefully you'll get a solution soon

 

443064076_hornetrelativetargetandownbra.JPG.2431132c872940edfe23c2a1c1807115.JPG

Posted

Here's roughly how I do it:

 

I know where bullseye is, and I know where I am.

 

Let's say I'm roughly 80 miles west of bullseye. If AWACS calls a bogey at 340 at 50 miles, I know that is slightly east and north of my position. I would turn 045 and start looking.

Motorola 68000 | 1 Mb | Debug port

"When performing a forced landing, fly the aircraft as far into the crash as possible." - Bob Hoover.

The JF-17 is not better than the F-16; it's different. It's how you fly that counts.

"An average aircraft with a skilled pilot, will out-perform the superior aircraft with an average pilot."

Posted

It may well be the case that the real JF17 doesn't have bullseye functionality.

 

Bullseye as we know/use it in the western jets is not universal and was likely bit of a new concept even in the late 80s in the US services. Pakistan, whilst using US aircraft, may have evolved different tactics and proceedures and therefore did not have a need for Bullseye integration in the JF17.

Posted
It may well be the case that the real JF17 doesn't have bullseye functionality.

 

Bullseye as we know/use it in the western jets is not universal and was likely bit of a new concept even in the late 80s in the US services. Pakistan, whilst using US aircraft, may have evolved different tactics and proceedures and therefore did not have a need for Bullseye integration in the JF17.

if you have a fully working datalink and shareable spi's/mp's you won't have to touch your radio ever again (well.. kinda :P) if you're not a controller, apart from when you want to make fun of your mates when they miss a target or something

 

the problems people are facing right now are:

- the datalink is only useful between jf-17s (it was announced that this would be the case before release / we work around it by just using jf-17s for now)

- threat enumeration is not working properly at all times (welp - it's EA and things like that are expected)

- there's no way to share spi's and/or mp's through the datalink (we work around this by either lazing/picking up through lss or sharing coords etc in voice)

  • Recently Browsing   0 members

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