reported CCIP line...

[Harlikwin]

On 12/25/2021 at 3:56 AM, QuiGon said:

!!!!!!!!!

It's one of the most frustrating issues in DCS and yet it get's seemingly no attention at all
It makes the Hornet almost entirely useless in the A-G role in a 80s setting like the BlueFlag 80s server.

 

Well the other issue for blueflag is that since ED changed how bunkers work, and and since there are no "dumb" bunker buster bombs (how hard would an unguided BLU-109 be to add) then blue is pretty much outa luck for older eras since the GBU31 is the only thing that works for blue.

Edited April 12, 2022 by Harlikwin

[QuiGon]

10 hours ago, Harlikwin said:

Well the other issue for blueflag is that since ED changed how bunkers work, and and since there are no "dumb" bunker buster bombs (how hard would an unguided BLU-109 be to add) then blue is pretty much outa luck for older eras since the GBU31 is the only thing that works for blue.

That's not an ED issue, but a mission design issue if anything. Besides the GBU-31 you can also use the GBU-24. Both are allowed there, so i don't really see an issue here.

Anyways, this is totally off topic, as this thread is about CCIP without GPS support in the Hornet.

[XCNuse]

Well, Wags just released a video on the Viper getting an ability to do INU fixing.

 

When can we expect this for the Hornet?

[Tholozor]

1 hour ago, XCNuse said:

Well, Wags just released a video on the Viper getting an ability to do INU fixing.

 

When can we expect this for the Hornet?

You can already do INS position updates in the 18, but they don't work quite according to documentation. The UPDT option is available on the HSI on the top row only if the position-keeping mode is not POS/AINS.

Edited June 21, 2022 by Tholozor

[HeavyGun1450]

And a year later since this thread has been made, and still nothing which is not surprising. It's been a bug with the module for years and it's never gotten significantly looked into or addressed by ED. A 1980s server I play on has to set the date into the late 90s because of this bug so you can use ifa to have a useable ins.

 

Edited June 21, 2022 by HeavyGun1450

[QuiGon]

9 hours ago, HeavyGun1450 said:

And a year later since this thread has been made, and still nothing which is not surprising. It's been a bug with the module for years and it's never gotten significantly looked into or addressed by ED. A 1980s server I play on has to set the date into the late 90s because of this bug so you can use ifa to have a useable ins.

Is it actually still an issue? I thought this was fixed when AGR was added.

Will have to do some testing...


Edit: It's actually still an issue. I just tested it (48 Minutes of flight without GPS):

Edited June 22, 2022 by QuiGon

[XCNuse]

14 hours ago, Tholozor said:

You can already do INS position updates in the 18, but they don't work quite according to documentation. The UPDT option is available on the HSI on the top row only if the position-keeping mode is not POS/AINS.

The menu seems to exist; but ED's documentation also states N/I, which I'm going to assume means "not implemented"

(and after fiddling with it just now, can indeed state that it definitely doesn't do anything)

Edited June 22, 2022 by XCNuse

[Tholozor]

1 hour ago, XCNuse said:

The menu seems to exist; but ED's documentation also states N/I, which I'm going to assume means "not implemented"

(and after fiddling with it just now, can indeed state that it definitely doesn't do anything)

 

Works fine on my end (at least this method, which again, is not fully correct per the NATOPS):
- Create TGT designation at desired location.
- HSI -> UDPT -> DSG -> ACPT
- A/C position is set to TGT position.

[dorianR666]

On 11/29/2021 at 9:16 AM, QuiGon said:

The CCIP inaccuracy is because of INS drift?

CCIP should work regardless of INS drift, this is a bug. Under no circumstances should the fall line be horizontal.

Edited June 25, 2022 by dorianR666

[QuiGon]

11 minutes ago, dorianR666 said:

CCIP should work regardless of INS drift, this is a bug. Under no circumstances should the fall line be horizontal.

Yes, I'm aware of it. It's been reported.

Edited June 25, 2022 by QuiGon

[HeavyGun1450]

On 6/25/2022 at 10:03 AM, QuiGon said:

Yes, I'm aware of it. It's been reported.

 

Hope to see it addressed in the near future!

[Crashdown2]

Oddly enough, I messed up alignment with stored heading, and waited the nearly 9 minutes for alignment, and the issue wasn't there. I've also noted that servers or missions with hot starts don't have this issue either, or rarely. Wonder if it's tied to the stored heading.

[QuiGon]

1 minute ago, Crashdown2 said:

Oddly enough, I messed up alignment with stored heading, and waited the nearly 9 minutes for alignment, and the issue wasn't there. I've also noted that servers or missions with hot starts don't have this issue either, or rarely. Wonder if it's tied to the stored heading.

I hot started, or air started even, when I tested this here, so no stored heading alignment:

On 6/22/2022 at 9:40 AM, QuiGon said:

Is it actually still an issue? I thought this was fixed when AGR was added.

Will have to do some testing...


Edit: It's actually still an issue. I just tested it (48 Minutes of flight without GPS):

 

 

[Crashdown2]

1 minute ago, QuiGon said:

I hot started, or air started even, when I tested this here, so no stored heading alignment:

 

I did say rarely as well with this, but sometimes I get lucky on hot starts. Keep in mind, the long alignment worked once so far. I don't have the patience to wait that long all the time :). Anyway, I am going to try it again when I get home. Make sure it wasn't a fluke.

[Crashdown2]

Just got home and tested it. Doing full alignment does not show drift or INS "mismatch". Stored heading will.  So if you like to go without the GPS correction, then you'll have to put in the 8min 53sec worth of waiting for alignment.

[QuiGon]

On 8/26/2022 at 3:44 PM, Crashdown2 said:

Just got home and tested it. Doing full alignment does not show drift or INS "mismatch". Stored heading will.

How does it show that?

[Crashdown2]

On 8/27/2022 at 10:24 AM, QuiGon said:

How does it show that?

Simply by flying around, and then engaging targets A/G with gun and slick bombs.  Right on target.  Stored heading will give you the headache of missing all the time and falling back on manual mode. I think it is the stored heading option of alignment that is bugged, not quite the INS itself. However I don't code and don't have access to it, but stands to reason that if full alignment works and stored heading doesn't....

[Shrimp]

Also, the INS is not computing wind (wind page shows 000/00), or is computing but not showing, which may be adding to weapons delivery calculations erros already reported elsewhere.

Edited September 25, 2022 by Shrimp
Punctuation

[Tomcatter87]

So, is there anything being done to make the Hornet able to hit anything with unguided bombs? Would be pretty neat, since it's kinda the point of an F/A-18.

[Cepheus76]

On 3/12/2022 at 9:26 PM, Hulkbust44 said:

Why would INS position data have any effect on CCIP calculations?

Sent from my SM-G975U using Tapatalk
 

INS also supplies attitude data.

[Fromthedeep]

24 minutes ago, Cepheus76 said:

INS also supplies attitude data.

INS drift doesn't make the attitude data invalid, so I don't understand why you'd have the DIL compensating for a phantom wind if it's using AGR for height above target calculations. 

[Cepheus76]

3 hours ago, Fromthedeep said:

INS drift doesn't make the attitude data invalid, so I don't understand why you'd have the DIL compensating for a phantom wind if it's using AGR for height above target calculations. 

You're right, I was shooting from the hip here instead of checking my references first.

In any case, I looked into said reference to refresh my memory and was reminded that a misaligned platform results in a cumulative track error, which results in a position error (duh). By implication, if the system calculates an incorrect track, the difference between actual heading and the incorrect track should be perceived by the system as a large wind correction angle. As a result, the DIL is displaced in such an extreme manner. 

[Lane]

I know it have allready been reported, but just for add and sorry i dont have keep a track as the bug was seems allready reported. It was seems to me it have been fixed on previous other beta.

As on Open beta as of 24-09-22 and second campaign mission (official one ). so pre GPS mission:, the CCIP Line is nearly at 90° on the right. Same bug as before.Fully aligned 

It is particulary a problem on the main campaign, as you cant change the date ( a workaround will be to copy the campaign  files, edit mission in editor. )

Edited October 10, 2022 by Lane

[BIGNEWY]

1 hour ago, Lane said:

I know it have allready been reported, but just for add and sorry i dont have keep a track as the bug was seems allready reported. It was seems to me it have been fixed on previous other beta.

As on Open beta as of 24-09-22 and second campaign mission (official one ). so pre GPS mission:, the CCIP Line is nearly at 90° on the right. Same bug as before.Fully aligned 

It is particulary a problem on the main campaign, as you cant change the date ( a workaround will be to copy the campaign  files, edit mission in editor. )

 

Please attach a track replay example showing this. 

Ensure your alignment is correct also, so INS is fully aligned (OK on HSI) make sure you dont move the aircraft or even take off the parking break while aligning.

thanks

[Lane]

Hi big Newy, im in european time, Switzerland Lausanne here, meaning working now so i will need find time tonight for do it.  

It is hardly a error during align procedure, the campaign mission start hot on the deck.

Edited October 11, 2022 by Lane