Jump to content

[REPORTED] 2.5.5 INS Not Aligning when on OPFOR


Recommended Posts

UPDATED LAST POST WITH TRACK FILE!

 

 

So many things not even sure where to start. Lots of new stuff in the hornet which is cool but almost felt like I didn’t even know how to fly it anymore. Exciting. The new sounds are super cool really enjoy those, integration of the EW system onto the radar screen is cool all the new gadgets there. All of the way points and INS seem to be totally messed up but I’m sure that’s just a glitch. Hope there are some training things coming soon and excited. What’s with the sim 9 saying aamram?


Edited by Ziptie

i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs

 

Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria

Link to post
Share on other sites

Well in the hornet campaign the fighter sweep mission has the waypoints / flight plan all messed up. Didn’t try another yet but still passed it. Jumped in the A10C and continuing to be blown away by the sound changes they made to that as well. Crazy different.

i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs

 

Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria

Link to post
Share on other sites

Try doing a cold start in the Hornet. Maybe the INS will work if it's aligned during a cold start. Or maybe it's a similar issue as with the AWACS, for the Datalink and you need to start a new mission for it to work. ED said they're revamping the INS system for the Hornet, so I bet it's related to that.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

1197644828_Screen_200911_044202-Copy.png.74d8c09ee9060cffd7408a75ab2c13ef.png

Z370 Aorus Gaming 7, i7-8700K, 3090 FTW3 Ultra, 32GB DDR4, 960 Pro, 970 Evo Plus, WD Gold 6TB, Seasonic Prime Platinum

F/A-18C, AV-8B, JF-17, A-10C (C II), M-2000C, F-16C, F-14, BS2, UH-1H, P-51D, Sptifire, FC3

Link to post
Share on other sites
Well in the hornet campaign the fighter sweep mission has the waypoints / flight plan all messed up. Didn’t try another yet but still passed it. Jumped in the A10C and continuing to be blown away by the sound changes they made to that as well. Crazy different.

 

Can you be a bit more descriptive than "all messed up"?

 

And a track will help as well.

spacer.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to post
Share on other sites

Sorry, they just didn’t show. Any combo of auto/sequence/wpt/ manual waypoint selection just nothing on HSI or SA page(s). When WYPT OSB was selected (and boxed WYPT show as it should once selected) - it would go some extreme 1xxx + mile distance away and seem to flash INS alignment numbers on MFCD like during startup. Stock stuff, no mods. Will try a repair and see if it does it again.

i7 6700 @4ghz, 32GB HyperX Fury ddr4-2133 ram, GTX980, Oculus Rift CV1, 2x1TB SSD drives (one solely for DCS OpenBeta standalone) Thrustmaster Warthog HOTAS, Thrustmaster Cougar MFDs

 

Airframes: A10C, A10CII, F/A-18C, F-14B, F-16C, UH=1H, FC3. Modules: Combined Arms, Supercarrier. Terrains: Persian Gulf, Nevada NTTR, Syria

Link to post
Share on other sites

INS BUG

 

Right after the update, not only me several guys we get this error. Moreover the Map can't be activated (appeared)

 

 

https://imgur.com/6NbmtpG

My Hardware: Z390 AORUS Master - Intel 8700K 3.7 GHz @ 4.9 ghz (Delid Copper IHS) - G.SKILL 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 2080ti OC 11gb - 2 EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27"

 

My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire.

 

My Maps: Nevada, Normandy, Persian Gulf, Syria.

Link to post
Share on other sites

I see you're using auto-start. Have you tried with a normal cold & dark start? I'm updating, but my internet is slow. I'll also test it out when I can

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

1197644828_Screen_200911_044202-Copy.png.74d8c09ee9060cffd7408a75ab2c13ef.png

Z370 Aorus Gaming 7, i7-8700K, 3090 FTW3 Ultra, 32GB DDR4, 960 Pro, 970 Evo Plus, WD Gold 6TB, Seasonic Prime Platinum

F/A-18C, AV-8B, JF-17, A-10C (C II), M-2000C, F-16C, F-14, BS2, UH-1H, P-51D, Sptifire, FC3

Link to post
Share on other sites

Look at your waypoint 0 coordinates, their at N0° and E0°.

 

The map is being displayed but probably no where near where your INS thinks you are. It thinks you are in the Sahara desert which is most likely why your waypoint is 3603NM away.

 

Could this be the beginning of a realistic INS ?


Edited by Rex854Warrior

[sIGPIC][/sIGPIC]

Link to post
Share on other sites

I thought I had it too, I might still. But I just tried to reproduce or see if I could find some pattern.

Usually, up until now, as soon as it would display 0.5 OK, I would switch it to Nav. Did that earlier tonight too, and I wouldnt get a map and it wouldnt know where it was. Waypoints were 4000+ miles away.

Then now I just did it again, and when it hit 0.5 OK, I left it and after 1½ minute or so, the map would appear, and all waypoints were correct, and the INS knew where it was again.

 

So yea, I guess some more steps have to be taken into account now. Havent read up on it in NATOPS or manual. I might tomorrow. Now its night night :).

- Jack of many DCS modules, master of none.

- Personal wishlist: F-15A, F-4S Phantom II, JAS 39A Gripen, SAAB 35 Draken, F-104 Starfighter, Panavia Tornado IDS.

 

| MSI Z87-G45 Gaming | i5-4670K @ 4.3Ghz | 32Gb DDR3 1600 | Asus GTX 1070 Strix OC | Samsung 850 Evo 250 & 500Gb | 40" Sony FullHD | Oculus Rift CV1 | Thrustmaster Warthog Stick (19.5cm extension) & Throttle | MFG Crosswind | Windows 10 |

Link to post
Share on other sites
I thought I had it too, I might still. But I just tried to reproduce or see if I could find some pattern.

Usually, up until now, as soon as it would display 0.5 OK, I would switch it to Nav. Did that earlier tonight too, and I wouldnt get a map and it wouldnt know where it was. Waypoints were 4000+ miles away.

Then now I just did it again, and when it hit 0.5 OK, I left it and after 1½ minute or so, the map would appear, and all waypoints were correct, and the INS knew where it was again.

 

So yea, I guess some more steps have to be taken into account now. Havent read up on it in NATOPS or manual. I might tomorrow. Now its night night :).

 

 

 

+1

Works for me too.

[sIGPIC][/sIGPIC]

Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.

Link to post
Share on other sites

I tried a cold start and the INS works fine if you let it align a little longer after it says 0.5 OK. After an extra 30 seconds (not sure, I didn't time it) it'll show the map and your coordinates.

As far as I can tell, the countdown happens faster than normal, something I suspected for a while now.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

1197644828_Screen_200911_044202-Copy.png.74d8c09ee9060cffd7408a75ab2c13ef.png

Z370 Aorus Gaming 7, i7-8700K, 3090 FTW3 Ultra, 32GB DDR4, 960 Pro, 970 Evo Plus, WD Gold 6TB, Seasonic Prime Platinum

F/A-18C, AV-8B, JF-17, A-10C (C II), M-2000C, F-16C, F-14, BS2, UH-1H, P-51D, Sptifire, FC3

Link to post
Share on other sites

Its (not technically) messed up, it is displaying in Degree Decimal Minutes (DDM) by default now. If you want it to display in Degree Minutes Seconds (DMS) like the last version you need to change it in the HSI settings...

 

HSI > Data > A/C, then on the bottom right "LAT LN SEC/DEG" this will change the coordinates from DDM to DMS, example:

 

N 43° 35.9873

E 39° 29.1238

 

to

 

N 43° 35' 59"

E 39° 29' 07"

 

If you select HSI > Data, on the bottom left "PRECISE" will give you decimal seconds for precision waypoints.

[sIGPIC][/sIGPIC]

 

http://www.csg-2.net/

Link to post
Share on other sites

I discovered that if you leave the INS powered off, map and WP's will appear after some time. You can then click INS to NAV and continue as always. Everything is ok.

[sIGPIC][/sIGPIC]

Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.

Link to post
Share on other sites
Dropped and air-start F18 in editor with one waypoint. Waypont was showing in-game over 4000 miles away.
Strange, I haven't had that

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

1197644828_Screen_200911_044202-Copy.png.74d8c09ee9060cffd7408a75ab2c13ef.png

Z370 Aorus Gaming 7, i7-8700K, 3090 FTW3 Ultra, 32GB DDR4, 960 Pro, 970 Evo Plus, WD Gold 6TB, Seasonic Prime Platinum

F/A-18C, AV-8B, JF-17, A-10C (C II), M-2000C, F-16C, F-14, BS2, UH-1H, P-51D, Sptifire, FC3

Link to post
Share on other sites

[REPORTED] 2.5.5 INS Not Aligning when on OPFOR

 

Eagle Dynamics/FA 18 Development Team:

 

While there have been some changes to the INS, the hornet will still correctly align when flying on for the "nato/blufor" coalitions on both Caucasus and PG map. However, when flying for OPFOR (Russian hornet, USAF aggressors hornet, etc.) and performing a cold start, the hornet completely refuses to appropriately align.

 

Using the normal alignment procedure (start up, switch to ground, wait for timer to countdown, switch to NAV, wait for HSI to display appropriate alignment) does not result in appropriate alignment of "OPFOR" hornets at any point in time. The HSI will continuously display all zeros for northing and easting, and waypoint 0 will always remain thousands of miles away. The heading tape will still function normally, but that is all.

 

This results in being unable to effectively navigate using onboard INS/HSI. The HSI map is not available obviously, and entering waypoints has been rendered useless. The F10 map has to be used as a means of obtaining range and bearing to targets (on servers that allow the F10 views). In addition, the datalink/SA becomes completely non-functional. The range displayed on the SA page is so far off from your actual location that absolutely no HAFUs will appear on the screen.

 

I have tested this on both public servers (Buddyspike and Growling Sidewinder) as well as user ran servers during a scrim with some friends. Any time a hornet spawned for cold start on OPFOR (for example: a Russian hornet at Beslan or Nalchik; or a USAF aggressors hornet at Bandar-Abbas) proper alignment could not be completed. I have not tested this issue offline, only in a multiplayer setting.

 

The effects of this could have severe consequences on upcoming SATAL matches for pilots that wish to fly the hornet as their SA would be severely compromised.

 

Thanks for listening,

 

Viper 9


Edited by Viper 9
Link to post
Share on other sites

I completely agreed, I investigated that problem using several coalitions, and only the red one presents this problem. The complicated thing is just for SATAL, since the RED coalition does not have information of the enemies or of the allies in the SA of the MPCD

 

picture.php?albumid=1712&pictureid=10868

[sIGPIC][/sIGPIC]

MB ASUS ROG Maximus XI Hero Z390 Intel Core i9-9900K NO COOLING, I love danger... (Just Kidding, EKWB water-cooling 4 CPU&GPU)

ZOTAC GAMING GeForce RTX 2080 Ti AMP 11GB RAM 64 M.2 1T SSD 2.5T ThrustMaster HOTAS Warthog Pimax 5K PLUS (8KX ASAP) Saitek Pro Rudder

Link to post
Share on other sites

I am also having the same issue, here's a trk file, I'll try to find other servers where the hornet is attached to "opfor factions" in game as that seems to be the problem. Welp I'll try and figure out a way to get the file size down :(


Edited by HoBo777
Additional info for context and clarity
Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...