Jump to content

Recommended Posts

Posted (edited)

I need help, since the BS3 update, I can’t get auto turn to target, to work. I get shval on target, lock it, hit auto turn and the helicopter seems to turn 90 degrees to the left of where the target is. I’m in auto hover, FD off.. am I missing something?

Edited by 504smudge

Eagles may soar but weasels don't get sucked into jet engines.

 

 

https://www.youtube.com/user/504smudge

 

https://www.facebook.com/504smudge

Posted (edited)

Someone correct me if I'm wrong.

Your INS system measures your position. It then uses your camera's angle and range finder to determine the targets location based on your INS location. SO, no matter how badly your INS is aligned, target heading hold should always work.

So somehow, our targeting system is determining the true exact location we're selecting, and our autopilot is then using the misaligned INS system to turn to where it thinks our target is, which is somewhere else apparently?

Edited by FusRoPotato
Posted
vor 5 Stunden schrieb FusRoPotato:

Someone correct me if I'm wrong.

Your INS system measures your position. It then uses your camera's angle and range finder to determine the targets location based on your INS location. SO, no matter how badly your INS is aligned, target heading hold should always work.

So somehow, our targeting system is determining the true exact location we're selecting, and our autopilot is then using the misaligned INS system to turn to where it thinks our target is, which is somewhere else apparently?

I think about it similar to some others, even if the drift is over 1000KM the new target point that I create should have exactly the same drift as my Helicopter, but it is not so and after retrieve this is completely different where.🥴

Posted
3 hours ago, Hobel said:

I think about it similar to some others, even if the drift is over 1000KM the new target point that I create should have exactly the same drift as my Helicopter, but it is not so and after retrieve this is completely different where.🥴

I tested both the last days in the mission editor. With realistic INS: Helo turning away from target when activating auto turn (like  504smudge descriped it)

Without realistic INS: Helo turning direct to the target, no problems.

Posted

Long press shkval unlock and it will turn. Not sure it is how it should suppose to be.

[sIGPIC][/sIGPIC]

I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A,

Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least

Posted

It does that for me too turns ccw from the target. Have not tried the long press shkval unlock yet. I use realistic ins alignment.

Posted

Having the same issue as well.

But I observed something.

Next time you are on hover and apply turn to target to target.

If the helo start turning right or left suddenly let it until it settles to a position.

Then switch the 3-WAY switch to top (MH) and adjust the knob for magnetic variation ( below the autopilot lights)

Adjust it to where the helo “should be facing” relative to your target .

Once there, flip the 3-way switch back to middle.

To be honest I don’t know if its the right or wrong thing to do, or if it messes something up; but its the only thing I found that helps me play the helo for now as a temp fix. When i finish with the targets and I am RTB i reset the magnetic variation to the original value for the particular map.


Sent from my iPad using Tapatalk

  • Like 2
Posted (edited)
32 minutes ago, mtd2811 said:

Having the same issue as well.

But I observed something.

Next time you are on hover and apply turn to target to target.

If the helo start turning right or left suddenly let it until it settles to a position.

Then switch the 3-WAY switch to top (MH) and adjust the knob for magnetic variation ( below the autopilot lights)

Adjust it to where the helo “should be facing” relative to your target .

Once there, flip the 3-way switch back to middle.

To be honest I don’t know if its the right or wrong thing to do, or if it messes something up; but its the only thing I found that helps me play the helo for now as a temp fix. When i finish with the targets and I am RTB i reset the magnetic variation to the original value for the particular map.


Sent from my iPad using Tapatalk

I think I will wait for the patch... 😉

Unfortunately, it wasn't in the last two patches these days.

Edited by v2tec
  • Like 1

________________________ ________ ______ ___ __ _

Win10 64 Pro, i7-6800K 3.4Ghz, 32 GB (DDR4), Asus Aorus 1080 TI WF, TrackIR 5 / RIFT, Thrustmaster Warthog, Fanatec Pedals, 55" oled 4k TV, Modules:A10C, KA-50, Huey, AV-8B, FA-18, F-16, NTTR, Persian Gulf

_ __ ___ ____ _____ ______ _______ ____________



Posted

Having the same problem. Thanks for posting.

  • Like 1

Ask Jesus for Forgiveness before you takeoff :pilotfly:!

PC=Win 10 HP 64 bit, Gigabyte Z390, Intel I5-9600k, 32 gig ram, Nvidia 2060 Super 8gig video. TM HOTAS WARTHOG with Saitek Pedals

Posted

I was pretty reliant on the "Auto Turn" feature for flying and targeting

The new BS3 implementation is totally screwed up it appears, and not sure how they did not notice this bug in testing (or at least indicate the new procedure if correct).

I will continue using BS2 until they fix it since to me the new features in BS3 is not all that much.

I do like the new counter measures improvement though in BS3.

Oh well, I hope they fix it soon and am confused as to why they would release two new patches since the time they released BS3 and would not have fixed this "Auto Turn" bug.

😞

  • Like 2
Posted

Adjusting the magnetic variation works as far as I have tested.

Posted (edited)

I have the same problem.

@Razor68 If it's about Mag.Var., why does AutoTurn work nice at first minutes of the mission and then work with lots of errors after some time?

Edited by Devrim

Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64)
Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR
>>MY MODS<< | Discord: Devrim#1068

Posted
29 minutes ago, Devrim said:

I have the same problem.

@Razor68 If it's about Mag.Var., why does AutoTurn work nice at first minutes of the mission and then work with lots of errors after some time?

 

I have flown some more and it is very unstable and annoying to use.

Posted

the hole INU is completly buged.... it starts with with the alligment thats not working,

-the heading is wrong,

- inu fix works only sometimes , and when it works the heading is also incorrect 

and this will make that the auto turn to target is also messed up.... 

 

we need to wait till its fixed.

 

Also shkval is tracking moving targets, even no "moving ground target" is selected. 

And the shkval have not changed since BS1 ... it dont track with contrast. it still locks objects  (it is cheating) ....

Im disapointed .... 

 

For me it look like , EDs 1st priority was releasing the shark before christmas , without testing his biggest new feature (the new Inu system)

Posted

ED said that INU had something wrong with cold start. So, prefer hot start for now.

Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64)
Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR
>>MY MODS<< | Discord: Devrim#1068

Posted (edited)

@Devrimi don’t believe that it will happens only in cold start, or that the problem with INU is related to the cold start procedure. I believe it’s more deeper inside of programming of the INU. Or that a bug in heading messes up the whole INU. 

Even in Hot Start the bugs occur.

Edited by Schlomo1933
  • Like 1
Posted

Same issue here. Also tried both magnetic and gryoscopic alignment as some videos suggested but it didn't matter.
Is it recognized as a bug ? Is there any workaround at least ?

  • Like 2
  • Recently Browsing   0 members

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