-Vindicator-

Ok, again, thanks a million to all of you for your great suggestions—I got it working! I’m sorry I didn’t get back to you earlier but I was tied up IRL. I checked for double-binding on the Trim switch, the UI layer for conflicts, and the axis assignment; no problems there and I could find no other conflict. I then tried Ironhand’s suggestion. The “Scan Zone Up” and “Scan Zone Down” functions worked fine with the keyboard commands (with or without the joystick plugged in) but the functions were still sticky when I used the joystick. So I simply swapped all functions on my Trim Switch to another switch and vice-versa, and everything’s fine! Thanks again!!

Thanks to all of you for your great answers! I’ll follow through and tell you how it went. Again, thanks!

I’ve been flying the F15c for many years but in the last several months I’ve been having problems with “Scan Zone Up” and “Scan Zone Down” on my joystick. My joystick is a Thrustmaster Hotas Warthog joystick. For the “Scan Zone Up” and “Scan Zone Down” functions I use the top right, 8-way, hat on the joystick. The joystick manual refers to that hat as the “Trim Switch.” To operate “Scan Zone Up” I move the hat up (“JOY BTN POV1 U”); to operate “Scan Zone Down” I move that hat down (“JOY BTN POV1 D”). The problem is that when I move the scan zone up or down in the VSD, the scan zone sticks. The scan zone information will show the high circle and altitude for the high elevation coverage limit, and the lower circle and altitude for the low elevation coverage limit, but frequently when I try to move the zone and circles up or down I can’t. Sometimes the upper and lower circles, and corresponding scan zone, disappear completely at the top of the VSD, and I can’t move the scan zone down. The problem doesn’t seem to be my particular joystick. I bought a new Thrustmaster Hotas Warthog joystick and experience the same problem with the new joystick. I’ve checked “Adjust Controls”; there is no double binding issue. I’ve plugged the joystick USB plug into a different port; I experience the same problem. I ran DCS Repair to no avail. I sent a “trouble ticket” to DCS on 12-26-22, but I have heard nothing back other than that the ticket has been accepted; I assume some delay is caused by the holidays. (My buying a new joystick is my problem and mine alone, but if the joystick is not causing the scan zone problem, I’d like to know so I can get a refund on the joystick before the refund period expires.) I could include a track but the most it would show is a sticky or frozen scan zone, or one that has entirely disappeared. Is this a bug? If not, does anyone have any suggestions as to how to fix this? (If I should have posted this elsewhere please let me know and I’ll post it appropriately.) Thank you!!!

As usual, Ironhand, thank you!!

OUTSTANDING FLAPPIE. Just what I was looking for! And thanks for everyone’s replies.

Is there a Caucasus map (preferably printable) showing roads (without obstructions like trees, telephone poles, etc.) that one can land an F15c (or other aircraft) on?

Lol thanks!

Got home, still foolin with it but got to 1509 kn gs lol

Outstanding, Ironhand. And thanks for the magic number. That’s the kind of specific info I was looking for. So I guess a remaining issue is whether an F15c can exceed 1494 knots ground speed in real life. If it can’t, then obviously the radar screen of DCS’s F15c is wrongly displaying 1503 kn gs. If an F15c can exceed 1494 kn gs in real life, the 1503 makes sense. I don’t know whether info on that real life issue is readily available, so I may have to just assume that the display simulates real life. Dying to get back home on my computer and fool around with this lol…. Thanks to all who posted on this topic.

Ok, thanks for your thoughts, Ironhand and Nahen. You’ve got me thinking. I’m not arguing with either of you but I do want to make sure I understand what each of you is saying. Let’s leave aside what the F15c can do in real life. And let’s assume for sake of discussion that the F15c in DCS cannot simulate exceeding 1494 knots ground speed and that a radar screen showing in excess of 1494 ground speed is wrong. Nonetheless, Ironhand clearly implies to me that his radar screen (right or wrong) SAID (caps for emphasis, not yelling) that he did 1503 knots ground speed. So, if I may, my question to Ironhand is: did your radar screen SAY you reached 1503 knots ground speed? And if Ironhand is saying that that’s what his radar screen SAID, my question to Nahen is: are you disputing that his screen SAID that? Thanks!

This is really interesting. Believe it or not, as I mentioned I thought I got it once to 1513-1514 kn gs, but could never duplicate it. Now maybe I know why.

No problem. Thank you Ironhand! 1503? Great! That’s what I wanted to know. Thanks Ironhand!

Thank you Draconus. I try to be courteous and your responses frequently are, but I notice that sometimes in these forums some folks, perhaps insecure at times, confuse demonstrating expertise with demonstrating discourtesy. I get the “manly military men insult” thing lol but I ain’t been drafted, DCS ain’t the military, and It should come as no surprise that people asking questions may err lolol. Ironhand’s been around awhile but he inadvertently misunderstood my question; folks err and that’s life. He also demonstrated humility. This is not a DCS issue but a character issue. I get it that people often unnecessarily argue with you in this forum, but don’t assume that’s always happening or assume a personal challenge when people pose a question; the question may simply reflect a mistake. 1. For example, one possibility you did not expressly discuss is that when I said, “your radar reflected 1507 knots ground speed,” I simply meant “your radar SCREEN reflected 1507 knots ground speed.” That’s what I meant lol. I’ve been trying to figure out why people say max gs is 1494 kn when my radar screen sometimes reflects more than 1494 kn gs. So I will simply assume that your radar screen reflected 1507 knots ground speed and that this is a bug lol. 2. For example, if you think your sentence beginning, “A bug is that even when aircraft air speed limit is hit the wind,” etc., is a model of clarity, I don’t what to say, but I tried to understand what you said and I think I know what you meant. 3. My question 3 meant to refer to radar “screen” and distinguish what the screen reflects or says the gs is in knots, versus what the gs really is. Apparently the radar screen can say 1507 knots ground speed even though in fact I cannot exceed 1494 knots ground speed. 4. Finally, please do not feel obligated to respond further; I’ve flown the F15 in DCS for years, I think I understand what you’ve written, and I will now monitor this topic, however long it continues, for any input by others only (although I think everything’s probably been covered). No problem. Thank you Ironhand! P.S. to Ironhand: It sounds like you’re suggesting this may not be a bug but related to altitude. I mentioned earlier that I was wondering if that was what’s going on. I’ll be away from my computer a few days, so If you try dropping to 30000 ft., etc., I’ll be very interested in what you find.

Thank you! I’m dying to see this but I won’t be able to access my computer until tomorrow. Do you exceed 1494 knots ground speed? I notice you mention “accelerating until you reach 1494.” Thanks again!

Correct. So just so I understand: (1) Your radar reflected 1507 knots ground speed? (2) This appears to be a bug? (3) So even if gs exceeds 1494 knots as reflected on the radar, I’m in fact not exceeding 1494 gs? Thanks!