BammBamm

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!

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

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 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?

I wish I had the firmware file, I would send it to you. My Joystick came with 1.07 and 1.09 base. Have you done a support ticket with them yet? They are actually pretty decent on their support. They will probably send it to you. It's not intuitive on how to get to the support tickets though. Logged into your account, go to customer service at the top, on that page, click on the black title on the left side that says TICKET. It will take you to your tickets. To create a new one, just choose one of the category options. Hope that helps,

Ya, it stops at 10 on the right and the left keeps going counting upwards for quite awhile and the RDY flashes continuously after a certain point. Is there a guide or new procedure to follow? What FIX is Tholozor referring to? Thank you,

FIX update methods? Could you please elaborate or provide a link. I fought with the ins alignment for hours yesterday watching WAGGS youtube alignment and not getting anywhere near the same result and it is way off when targeting and waypoints by about 6 miles or so. Mine also gets to about 10 and stops. I literally followed his instructions to the exact T several time and several game restarts and even a install repair and also a complete reinstall on a seperate machine. Same results every time. Am I missing something here? Is it supposed to stop at 10 now and be off that far? lol.

I am also experiencing this issue. Mine is updated, but the next release will have to be manually done until they resolve the lookup in SimAppPro.

BoundaryLayer, you are correct, I mispoke. Technically, I have 21 as well. I forgot I copied, renamed and modified a few of them so my numbers are rearranged. Wasn't thinking, it's actually lesson 18 like in your image. Sorry about that, doh!

I'm glad I'm not crazy. Please see the video for proof it existed before. At 5:15 he cycles through the features. Thank you,

Greetings, In training mission for the F-16C "Lesson 24 - JDAM Employment" at the very beginning of the mission when he says to switch to the CNTL page on the SMS and then select the OSB that has AIR next to it and change it to Ground mode, the button does nothing, it doesn't change. Is anyone else experiencing this issue? I went to WAGS Youtube videos and it's working great in all his JDAM videos on his SMS page, so I don't know if it's isolated to me or if nobody has noticed this isn't working anymore. Thanks everyone,

Thank you, yes. I have tried that as well. It seems to be limited by a proportional connection of x_trans and viewAngle (FOV). If I change the FOV or viewAngle property to reflect what I want it to be, it works fine, for example, 110 degrees. In fact, Alt + Num0 sets that value. Then if I go in and try to set the zoom out with x_trans = 0.20 it will honor the x_trans and zoom me out to where I want it to be, but it overrides and ignores the FOV setting and makes it large again.

Greetings and Happy New Year, I have been very reluctant to post this query as I am independent and hate people that just jump in and ask without figuring it out for themselves. Usually, the answer is out there, but unfortunately, after searching and testing for 3 days now, I'm reaching out for help. I have the saved games server.lua, views.lua and SnapViews.lua files configured as best I thought per my understanding of the syntax, but I cannot achieve what I'm trying to do. Let's use the F-18, for example. If I set the snap views x_trans property to = -0.01 I can get the zoom back that I want. However, it will not play nice with the camera zoom (RCtrl + Num/ and RCtrl + Num*). The viewAngle = command when set at 180, will provide the view of the HUD I want with the projections scaled down instead of being covered up by the sides. I have a Samsung 49" G9 curved widescreen and the limited zoom vs camera zoom is very limiting, I am so far forward that the left and right verticles of the cockpit cover my view and if I zoom out all the way, I can't see all of the HUD on the left and right. I have found there is some sort of limitation somewhere I haven't found yet that keeps the x vs z relationship limited. I can have one or the other, but not both. I have read all the explanations and theories and even some people that have said it's not possible, but I have seen a couple forum posts where someone complained about the zoom with a screenshot showing a tiny hud and zoomed back behind the seat. I have altered the limits_6DOF to allow my camera zoom as far in as the runway and as far back as the tail, but I cannot find the setting that unlocks the basic zoom level forward and back or x_trans = value (Num / and Num*) I hope that made sense. Please keep this mature and on topic. I can explain why I need this or what's wrong with the normal view in private messages, if necessary. Thanks everyone, Bamm

Here is a couple pics of the new OEM TM Throttle Slew that came with my HOTAS Warthog. I bought mine about 4 months ago, if that. It looks similar to the Delta.