Viper 9

League: Gold Squadron Name: Viper Squadron Discord: https://discord.gg/Fn86gM Contact person: Viper 9 | Defector Aircraft Selection: F18, J11, F14, Jf17, F16... Roster: Defector Maximus Phantom Infected TaxDollarsAtWork Arkangel Le Hai Ruskov (Rosco) and others... :)

These two guys are in the server spouting racist and hateful comments at people flying against them. Ruins the fun of the server. Very offensive language that is against server rules, while everyone was trying to have a civil discussion.

This has been an issue for a long time. If something else is on the same bearing as a target you are trying to lock up and is within the current scan area of your radar elevation setting, then you could lock up something you did not expect. It happens even more frequently when using AACQ. Not sure if it's really a "bug" or just an unfortunate consequence of using the hornet's radar. Maybe in real life, the radar is intentionally programmed to ignore and avoid STT locks on targets outside of the current range setting.

Hornet INS NOT Working On OPFOR - Chapter 2 This bug has returned: 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 There may be some subtle differences from before (This was originally posted a few months ago when this bug first became apparent). But the Hornet not aligning bug has returned for any hornets playing on OPFOR coalitions (Russia, China, USAF Aggrsrs etc.). This bug is present regardless of whether or not the targeting pod is loaded, which may be in contrast to another bug report recently. SATAL matches are this weekend and, without a working SA page, hornet drivers will not be able to effectively compete as they normally would. Do I have to go through the trouble of making another track file?? The problem is almost identical to the one I reported a few months ago. :mad::mad::mad::mad:

Hey did see my message? Just wondering what I need to do

Hello, what are the steps I need to take to be unbanned from this server? Ive been playing a lot and I want to start fresh on this server. I have been banned for 1 year now. I've tried messaging Drex but he has not responded to my messages.

I was really hoping you guys were going to fix this by the time another update rolled around.... update released today and the INS for opfor hornets is still completely dysfunctional. SATAL is compromised...

That was the very first thing I did to try and trouble shoot it. didn't work :(

has anybody looked into this?

Hobo was nice and helped me record a track, see the post above! Thanks!

Im having issues recording a track for some reason, sorry, give me a bit of time.

Yes, coming up shortly

[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

Viper Squadron Application Gold League Application: League: Gold Squadron Name: Viper Squadron Teamspeak/Discord: https://discord.gg/GQF9z3 Contact person: Defector or Infected Aircraft Selection. 2* F18, 1* SU27, 1* F14 Pilot Roster: Viper 7 | infected (Iran +2:30, Zulu) Viper 21 | Witch Doctor (England, Zulu) Viper 22 | deer(England, Zulu) Viper 17 | Rosco (United States -6 Zulu) Viper 9 | Defector (United States -9 Zulu) Viper 66 | Joystick (Switzerland +1 Zulu)

I highly doubt that.

DDCS is horrible, I was banned from there as well. I tried to speak out multiple times about people being absolute sh*theads in the server and being offensive. I was banned for it. The discord is a cancer, full of people who love to hate on newbies. The people on there are also racist and very offensive. On top of that, the server has been running like crap, and overpowered SAM defenses are spammed everywhere, making the gameplay and progress painfully slow and boring.

Is the AGM65G being taken away? :O I was reading through the hornet mini updates board and discovered that the MavG may be getting replaced with the MavF? My concern with this is that I really enjoy using the force correlate feature on the MavG. Does the MavF have this? or are we going to lose F/C completely? :helpsmilie: