BammBamm

Ya, this is pretty bad. They really need to host updates and larger files on a cloud based service like S3 so that people can still get logged into the game and browse the website. Whoever their head IT guy is needs to be ejected without a parachute, this is very basic networking 101 that a kid out of college would have caught. We are going on almost 8 hours now of this. It's laughable at this point.

Ya, well, I think this is a little more than Sinai. The website is down too. It's like they are either having issues with the same circuit for both the website and the game servers or they are the victim of a DDOS, because I can't get to anything at all. Every time I start the game it times out with a 502 error and disables all my modules. Been like this for over 2 hours now and I have fiber through Frontier, so before anyone asks, no, it's not my Internet, because I obviously had to be online to post this

Want to see something funny? Load up the Hornet with the SLAM-ER and the datapod. Get it all set up, inst fuze, man launch, too, etc... Then launch the missile. watch it travel through the DDI. Then at about 14.0 seconds before impact, notice the screen change. Now, hit F6 (follow missile view) and see a high quality picture in that mode. Switch back to cockpit F1 and it goes back to an all dark screen with a couple hot objects. Keep switching back and forth. Easily reproduceable. See attached image. I can't wait for the next retort that this is by design realistic and real pilots jump out of their cockpits onto the missile to get a better guidance picture just like Harry Potter on his Nimbus 3000.

lol, that's a really good point!

How many of you people experiencing this all have their additional monitors on the left side? I'd be willing to bet all of you. Move them to the right, adjust the code to reflect the new coordinates and I betcha your issue is resolved. If you need help with it or don't understand what I'm saying, PM me. But I figured out what was causing it about a week ago and just edited the code to fix it for myself.

Thank you for your feedback. I agree with you, it's been a great product up until this latest incident. I have been an IT Engineer for over 30 years now and I've troubleshot this myself. The biggest tell tale sign that it's the base control board is that it happens after a period of time and then happens over and over. Typically, this points to an overheating issue or a cold solder. (Cold solder is when there is a crack in the solder circuit somewhere and when it heats up and expands, it creates an air gap causing a temporary disconnect.) I haven't seen any bad solder joints, it all looks good and the firmware isn't available to download, so without voiding the warranty, I've gone as far as I can go. Are you experiencing the same disconnect after a period of gameplay time and then it happening several times? The other thing it could possibly be is a memory leak or buffer overrun. I have noticed also that when there is a very high load on the joystick I/O it will cause it to happen as well. Like it can't keep up or there is a bug in the firmware and a disconnect, reconnect kinda flushes it or resets it. This is all theory though, so who knows. They claim it's a cable in the base, which I don't see how that's possible. I've never seen this behavior from a bad cable contact.

Regretfully, I feel it necessary to make the community aware of the most recent experience I had with WinWing as well as 3 other people that have experienced the same issue and their unwillingness to resolve it. I own over $2100 of WinWing products, the throttles, joysticks, extensions, etc.. I have been happy with them for the most part and had zero issues. Just recently, the Orion2 joystick base started disconnecting and reconnecting from the USB bus over and over. I created a ticket and sent images and proof as well as performed all the tasks they asked for the resolution even though I knew them asking me to plug in the base by itself without the joystick attached and play the game that way to see if it happens again would not prove anything, let alone be possible to even do. How can you fly without the joystick portion? Anyway, after going back and forth with them and even asking for the tiny little circuit board that cost them less than a dollar to make to be replaced to resolve the issue, all they were willing to do was send me a word document on how to unplug and plug back in the cables. They informed me it was past the 14 day return period and that was it. They said sorry for the inconvenience and will not do anything else. They know they are in another country and cannot be held accountable and unfortunately, their attitude and actions reflect that. I am now stuck with a $ 300.00 joystick that doesn't work from a company that will not spend any money to resolve the issue. I sincerely hope nobody else experiences the same issues and this notice helps someone else avoid going through this.

Awesome, thanks guys! I appreciate the help.

EDIT: Disregard. You're 100% right. After understanding the radar functions better, it seems to be working now that I have it adjusted correctly. 1 bar and middle azimuth with a tighter elevation was the trick for that distance. Thanks and sorry for the unnecessary post.

Could somebody please watch the attached track and educate me on what I am doing wrong here? This is one of the training lessons, so it's really hard to screw it up, but apparently I have done so. All I've done is select AA mode and fly. Radar is on and working, Master Arm is on and it's also not in quiet or silent. It never once picks up the SU-27. Thank you, Lesson 12 - AIM-120 BC Air-Air Missles.miz_20032023_09-37.trk

Meh, to each his own. I don't blame you though, the built in game design settings and "realism" of unlimited ammo, unlimited fuel and immortality are very appealing.

Ka-50 Black Shark 3: Colored TV screen That's not a bug as far as I'm concerned. If they take 3 years to get to this one and put it at the bottom of their list, it wouldn't hurt my feelings any. For the ones with external MFCD monitors experiencing the shadows or the vertical boxes on the left or right and/or the labels issues not displayed in the correct location on your main screen, The solution is very simple.. It's an X, Y coordinates issue with relation to the center of the screen and where DCS thinks the center of the screen is. The dark lines and boxes you see are shaders supposed to be for the entire screen, but are being moved left or right due to the center of the screen not calculated correctly. One line of lua code fixes it and it doesn't break it on the ST version either. Just calculate your screen center in relation to your external monitor screen size and resolution and modify the monitors config.

I also had this issue. Try adjusting the x, y values for the viewport. I was able to resolve mine doing this by changing center in relation to the other 2 monitors.

I had the same issue. I was able to resolve it pretty easy with adjusting the x, y coordinates of the viewports.

I enjoyed mission one and would like to enjoy mission 2, but if you do purchase this, make sure you bring some popcorn, a pillow and a good book to read because if you take off too soon, you fail the mission and if you start up properly, radio on the correct station and can hear radio traffic, the wait is longer than I have been able to find out yet. I let it sit for about 3 hours and it still wouldn't tell me to take off, so I'm guessing it's either a bug or there is a hidden trigger that isn't obvious like configuring the flares a certain way, choosing the correct livery or weapons set to man instead of auto. Who knows. Anyone else had this happen to them?