Jump to content

Recommended Posts

  • ED Team
Posted
13 minutes ago, Lane said:

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

No rush, have a good day.

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted (edited)
3 hours ago, BIGNEWY said:

No rush, have a good day.

I had a bit of time during lunch. So i have do a quick test:  And now it seems fixed. 

Let me dig in. 

  •  I had update friday to last Openbeta. ( no idea is something have been changed  in this regard)
  • I have reset the campaign 
  • Hot start on the deck, the INS is on Nav, Quality 0.5 : OK when launch the mission
  • Switch INS to IFA, timer start.
  • Waited 2 minutes and take off. (surely not necessary)
  • CCIP reticule is aligned correctly, no drift, look totallly ok. Same in Auto.

I will need do further test and save track if i encounter the problem again. I am ofc conscient that the best is just provide track for exclude any user error and report can just make thing more hard to debug.

Edited by Lane

- I7 2600K @5.2ghz ( EK full Nickel waterblock )

- Gigabyte P67A-UD7 B3

- 8GB Predator 2133mhz

- 2x HD7970 - EK Nickel EN H2o block

- 2x Crucial realSSD C300 Raid0

- Black Widow Ultimate - X52 -TrackIR 5

- XIfi Titanium HD

- Win 7 x64Pro

 

Posted (edited)

for the mission i recall, honest i dont remember and i have sadly no save the mission in the editor. so i have do some try: one quick mission set at 1989 and 2012 with winds ( 30 knots)

Was dumb from me, my error is just that i was switch the INS from NAV to IFA in 1989 mission.

3 tracks:

in one 1989 i switch to NAV to IFA, not in the second one.  In the 2012 all is ok with IFA allready set.  

tst_CCIP_2012_b .tst_CCIP_1989_b_nav3 .trktktst_CCIP_1989_b_ifa2 .trk

This is only quick test, and with a bad hotas, i was not really search to fly so be indulgent and the margin of error is big.

I will need test the campaign mission for see if it same, but i ask me if it can be just linked to it. I hope it have not bring more confusion that it was allready

Edited by Lane

- I7 2600K @5.2ghz ( EK full Nickel waterblock )

- Gigabyte P67A-UD7 B3

- 8GB Predator 2133mhz

- 2x HD7970 - EK Nickel EN H2o block

- 2x Crucial realSSD C300 Raid0

- Black Widow Ultimate - X52 -TrackIR 5

- XIfi Titanium HD

- Win 7 x64Pro

 

Posted
On 10/11/2022 at 2:00 PM, BIGNEWY said:

could it have been INS drift?

no matter the drift, the line shouldnt be horizontal like that, so this is a bug.

  • Like 1

CPU: AMD Ryzen 5 1600X

GPU: AMD RX 580

  • ED Team
Posted
On 2/3/2023 at 9:56 PM, dorianR666 said:

no matter the drift, the line shouldnt be horizontal like that, so this is a bug.

Hi, 

do you have any public evidence of when it should be like when the INS is not aligned correctly? 

If so please DM me, so I have something to show to the team

thank you 

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted
3 hours ago, BIGNEWY said:

Hi, 

do you have any public evidence of when it should be like when the INS is not aligned correctly? 

If so please DM me, so I have something to show to the team

thank you 

This happens even with a correctly aligned INS. It is already reported and well documented here:

 

  • Like 1

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

  • 4 months later...
Posted

Hi,

Hot start on carrier, IFA for the navigation system all the way and this happens when I get to the target (same if i put it to NAV): The CCIP fall line and cross is always deviated form the vertical. This time is nearly 90º to the right O_O.

What I am doing wrong?

Thanks in advance!

 

 

Sin título.png

Posted (edited)

Looks like it's a mission without GPS which leads to INS drift and the result is this ancient issue that you see.

Can you confirm that GPS is NOT available for the F-18 in the mission you played?

Edited by razo+r
Posted

this looks like CADC failure. what was the winds aloft in this mission?

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted
1 hour ago, razo+r said:

Looks like it's a mission without GPS which leads to INS drift and the result is this ancient issue that you see.

Can you confirm that GPS is NOT available for the F-18 in the mission you played?

 

ummm, you are right. The mission was intended for the F14 tomcat in 1992 and I changed the player aircraft for the f-18.

BTW, there is some way to avoid the drift?, besides resheduling it for a more recent date I meant

Thanks for the help both of you!!!

Posted (edited)

Whoever tagged this as no bug needs to read through the reported bugs again.... 

 

2 minutes ago, daemon1808 said:

ummm, you are right. The mission was intended for the F14 tomcat in 1992 and I changed the player aircraft for the f-18.

BTW, there is some way to avoid the drift?, besides resheduling it for a more recent date I meant

Thanks for the help both of you!!!

You might be able to fix it by doing an INS update manually. But the drift itself cannot be avoided, it can only be corrected over and over again. 

Edited by razo+r
  • Like 6
Posted (edited)

@BIGNEWY I don't know who added the "improper alignment" tag, but as @razo+r has said: this is not due to improper alignment, but is actually a long standing bug with the Hornet's INS. If GPS is not available the INS will drift (which is correct) and will mess up the CCIP line, even when using AGR (which is a bug).

It's well documented in the following thread (also reported by CBTs) :

 

Edited by QuiGon
  • Like 6

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

  • 4 months later...
Posted

I had some 83XRT and CBU-99 loaded.  I set up the parameters (CCIP, nose fuze etc etc) but after I did the CCIP bomb drop line in straight and level flight was not vertical straight down.  It was skewed to the left at an angle.  Did something go wrong?  Did I pull too many Gs and mess the sensors up?

v6,

boNes

"Also, I would prefer a back seater over the extra gas any day. I would have 80 pounds of flesh to eat and a pair of glasses to start a fire." --F/A-18 Hornet pilot

Posted (edited)

Are you by any chance flying in a non-GPS environment or using INS only (INS knob at NAV instead of IFA)? The INS drifting seems to be influencing the CCIP pipper, which is a bug that was reported some time ago.

Edited by razo+r
Posted

Actually,i think it was.  I have video footage, I'll go back and check.


Thanks for the idea!

v6,

boNes

"Also, I would prefer a back seater over the extra gas any day. I would have 80 pounds of flesh to eat and a pair of glasses to start a fire." --F/A-18 Hornet pilot

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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