miguez

Hey Ragtag, I just found out that 6.6.1.15 is what shows in the About from the Profile Editor. In the About from the Control Panel (not the Windows Control Panel, the Game Controller Control Panel which you get to from right clicking on the Saitek icon in the taskbar and chosing Control Panel) it shows as: Driver Version: 6.0.4.1 Software Version: 6.6.0.38 I wonder what that software version refers to...?

That depends totally on the mission (ferry vs. combat, for example), and the amount of realism you want in your simulation. ED just simulated what the real thing has, it's up to the pilot to use it or not.

Hi guys, The following is my understanding, but I am not 100% sure on it yet, need more testing. VNAV does work, but it is not followed by the AP, as far as I know. Where it does show is when you use the FD mode of the AP, which is for hand flying. In FD mode, there are bank cues, to guide you through the route you have programmed, as well as vertical cues, to achieve the altitude programmed in your ABRIS. Other than that, when not in FD mode, the ABRIS will give you the required vertical velocity to achieve the programmed altitude at the programmed point. That would show on the NAV page of the ABRIS, on the bottom 1/3, where you can see distance to waypoints, cross-track error, etc. Best regards,

@ Ramstein, Yep, as you can tell from my previous post, I kept the same drivers (I guess you could say I RTFReadme ;)). @ bumfire Which SST software version are your unning? The last two I tried (version numbers mentioned in my previous post) both accept the different modifiers. Still no joy, though, I now see that when I use a Right modifier it does show as "Right Alt" in the Profile Editor, but BS still won't take it. Any other ideas? EDIT: All is working now. I installed 6.0.10.7 yesterday, it didn't work, then today I decided to re-install 6.6.0.38 for the third time, and all of a sudden it is working. Maybe something was up with the Magic Keyboard? That gets re-installed every time I swapped versions... Well, thanks for the help, but unfortunately I can't pinpoint what it is that made it work.

No joy with version 6.0.10.7 either. Should I be seeing any notation that the "Alt" key that shows in the Profile Editor is the Left or Right one? Even without seeing it, it does not work in game. The drivers (6.0.4.1) for both of these versions are the same, they are the latest drivers, so I kept the same driver installed.

Hi Mastiff, It's actually RShift + L. RShift + J turns on or off the Anti-Collision Beacon.

Hi CyBerkut, Thanks for the tip, I'll try the older one. By the way, the latest is indeed 6.6.0.38. Saitek says 6.6.1.15 on their forum, but after install, check the About on the Control Panel, it will say the number I mentioned. Best regards,

Hi Kurtz, Thanks for the ideas. The problem is that if I simply assign buttons to actions inside DCS, I lose the Modes feature. With this feature (if you are not familiar with the X52), I can have each button behave in three different ways, a separate keypress for each of those ways. it basically triples the number of buttons you have. Thanks,

Howdy, Found threads via the search on this, but they all say that Left or Right modifiers (Ctrl, Shift, Alt) are detected by the latest X52 SST. I have version 6.6.0.38, which is the latest one they have in public beta, which is obtained via the Saitek forum. It doesn't seem to recognize Left or Right modifiers, keys just show as "Shift" or "Ctrl". All assignments with Shift, Ctrl, or Alt do not work in the game, after programming in SST, and I am pretty sure it is because there's no distinction between Left or Right. Any ideas on how to get this to work? Thanks,

English manual page 2-55: "Landing Lights and Voice Warning ("Betty") Control Panel The landing and voice warning ("Betty") control panel is located in the lower part of the center panel. It controls landing lights, navigation channels, and the automatic voice message unit (VMU). The landing lights are used to illuminate the landing position in the absence of lighting on the ground. The landing lights are located underneath the fuselage and can be slewed. 2-41: Landing lights and voice warning ("Betty") control panel. The lights and VMU panel contains the following functions: 1. “ОСН-РЕЗЕРВ” (Main and backup landing light switch). To select either the main or backup landing lights, set this switch to the "ОСН" position to turn on the main landing light or select the "РЕЗЕРВ" position to select the backup light. [RCTRL + L] Note that both lights can also be controlled via the "ПОСАД ФАРЫ" switch on the collective, independent of the "ОСН-РЕЗЕРВ" switch position. Additionally, you may slew the main landing light by holding down the right control key and pressing [;], [,], [.] and [/] 2. “УПР. СВЕТ – УБОРКА” (Landing light ON/OFF switch). This is a three-position switch that controls the main landing light. The “УПР СВЕТ” extends the light and turns it on; the middle position turns the light off, and the “УБОРКА” position will turn off the light and retract it. [RSHIFT + L]"

Hi Buznee, I have a couple of answers: My Shkval is assigned to POV Hat 2, but I did it in game, not via SST. The X52 throttle quadrant has a round metal knob on its left side, which is supposed to adjust the strength needed to overcome the idle and afterburner detents, give that a try.

OK, quick update for whoever is interested: Have been flying with both the X52 joystick and throttle. I still plan to go back to the MSFFB2 for the stick, but I wanted to give the X52 stick a fair run. Trimming is definitely tricky without force feedback! I got the hang of it, but the sim feels very different with force feedback and, in my opinion, better. Hopefully Saitek will make a force feedback X52 stick in the future. I had some problems with programming the buttons via SST in the beginning, but it was due to incompatibility between the drivers and the SST versions I had installed. After installing the proper driver versions, everything worked. The programming interface in SST (the latest beta version, which you can get here) is very nice, and very intuitive. I had no problems getting buttons assigned. My biggest problem is deciding what keypresses go where. I started by looking at what the real collective and cyclic sticks have in the Kamov, and used most of those, but then added a lot more, since the X52, with its 3 modes and shift capabilities, has a LOT more possibilities than the real helicopter sticks. Right now, following a suggestion from this forum, I have Mode 1 as my Startup/Takeoff/Land/Shutdown mode, Mode 2 is my Climb/Cruise/Descent mode, and Mode 3 is for Combat. I added pertinent keys to each mode, then flew the sim sometimes and kept track of whatever I had forgotten (and therefore used the keyboard), and added those too. All in all, I am very happy with the hardware and software, and consider it a $100 bill very well spent. Thanks to everyone who helped me on this, and I hope this info might help someone in the future. Best regards,

Great suggestion, thanks!

Yep, I have done this too, approach a tank which is firing at me with main gun (from afar), then machine gun (closer), then nothing (really close). It seems the AI has a minimum engagement distance even for smaller arms.

Yep, that's the EKRAN way of recommending anti-icing, and it means both rotor and engine. Turn both on and you'll have no problems.

Excellent attitude! We're all learning here, so going through these things helps everyone out. Pretty soon you'll be helping me :).

Hey docehrenhoefer, Have you tried flying it again? Is it reproduceable? Always at the same point/altitude/time?

Hey Sinner, I think in real life, for the majority of the time, the pilot is the one entering these waypoints in the PVI-800, it isn't done for him, and so, as you mentioned, this would be one of the things you do in the pre-flight phase. Also, sometimes a CAP will be requested to check out a LAT/LONG given by a ground or airborne observer to the Forward Air Controller, and you'll be wise to enter it for accurate navigation. My train of thought, at least.

No. Check here.

Now THAT is realism!

Hi Sunjah, If you have heat Blur turned on, you should see it at all times, from the moment the engines come on. It does not take a certain amount of time before you can see them. Best regards,

Hi Sunjah, I have PMed you to check this thread :). The reason to keep the answers here is to make sure other people can find out the same answers you are looking for. So, with that in mind, let's start the troubleshooting: 1 - Ensure your INU and INU HEAT are on. they are located on the Rear Auxiliary Panel. 2 - Ensure you have reset your weapons mode by hitting the RESET button, located on the Targeting Mode Control Panel, right next to the switch to put the laser in OFF or STBY position. You can achieve the same by hitting Backspace on your keyboard, if you have not changed that default key assignment. Let's go from here. Looking forward to your answers, so we can fix this :).

Hi Crow Bar, In normal conditions the engines don't produce any smoke. If you are hit, and the engine is damaged, it may produce light gray smoke. The same goes for AI helicopters and airplanes. Is that what you were asking about?

Hey Yellownet, Good question, I have updated the original post with the info and added the price too!

For the record, but you should not have to use activation/deactivation for a Black Shark uninstall/reinstall procedure, from what ED says here. But maybe in this case it can help? Maybe the sim is not behaving during uninstall/reinstall as it should?