PiedDroit

See my replies in bold.

Mk108 round was very slow and contained a lot of explosives (very thin shell), it was more heavy than DEFA's (330g vs 275g), this gun was more comparable to an automatic grenade launcher. It's best to compare DEFA against modern guns. P.S.: I'm not saying there is nothing wrong. I agree that DEFA should be as deadly a the SU-27's gun, and therefore it feels a bit underpowered now. But comparison with Mk108 is a bit too much. See link you posted, I quoted it on page 1 of this thread and sums it up nicely I think. Compare with this.

There was another thread worth reading on that topic, with the info there it can reasonably be assumed that it should be rather equal to the SU-27's gun. DEFA 554 Stopping Power

You're welcome, to know which TACAN to use, you can read this document (I told to go on Kutaisi because it was the only station I could remember): \DCS World\Doc\Charts\DCS_GND_Charts.pdf TACAN stations are marked with triangular symbol and are also indicated in the bottom of each chart (search for "TACAN"). For more TACAN stuff I guess you can refer to documents that were written for A-10C as it is pretty much the same (except maybe for the number of channels you can use). The manual will tell you were the panels are, maybe more stuff will be added later.

Kutaisi airport. Hot start. Dial X44 on tacan panel (the rest is setup by default, power and mode). Select "TAC" on HSI with knob that looks like a pitchfork. This basic setup will allow you to test it. I don't know if its works with air to air in the current version.

Ah my bad sorry about that. Thanks for the info. I thought I read something different, it was a while ago.

Not true, a saturated RWR won't be able to get accurate direction. That kind of sensors have reception lobes that can pick up a strong signal and give false indications.

about that VENT, it's actually VENT: OFF/G/D (not VENT/G/D). I confirm that for first part of start up you need to use that red button to make sure throttle is back full

Voted yes, it's a very nice little COIN aircraft. It's a soft yes though, if it is completely overwhelmed by a Super Tucano or a Bronco I would probably skip it but given it's specs it seems reasonably comparable.

I just checked, looks like it's the same threshold bug, tuning it back to normal curve brings it back. Problem is, when that threshold is passed, it goes very fast, there's no way to make it slower. Try vertical axis with saturation Y = 60, it will start moving only at max value. EDIT actually, it's possible to tune it despite of the threshold, I tried this for vertical: Deadzone 0 Saturation X and Y both 100 Curve 0 Invert User curve 50 to 100 by increments of 5

I think TDC currently only moves if in the upper 50% of the curve, so if you try to tone it down it doesn't move because your values are below the threshold. The bug I'm talking about is already reported. I didn't try in latest update though.

Actually to use it with autopilot you need to use Shkval. First lock your target with TV, then activate laser ranging. Then activate autopilot, the aircraft will fly towards the target by itself (mode is called "combat steering" iirc). Only thing left to do is press fire button (keep pressed) until the bombs drop. SU-25T is definitely more capable. SU-25A is more fun.

Default zoom can be adjusted, so this kind of setting is very specific. I prefer to keep my zoom slider linear. It's a matter of taste.

In Mirage-2000C controls, "All", the exact name is "VTB Viewport ON/OFF", sorry about misleading you to look for "Toggle" :music_whistling::D

It was reported in bug section: http://forums.eagle.ru/showthread.php?t=161433 To see it in cockpit view you need to bind a key (Toggle VTB viewport)

Yes, it should be showed by default to match other A/C behaviour. While retaining the ability to hide it with the shortcut please :)

You're welcome :thumbup: You might want to use saturation X to create a kind of deadzone at the end of the joystick's range. Let's say your throttle is a bit wobbly and never goes fully 100% Or maybe you don't feel comfortable pushing the stick full right so you'd prefer the ingame stick to reach maximum deflection before hitting maximum physical limit. Saturation Y is used when the maximum deflection in-game is too much for you. For example, a TDC is moving so fast that you can't control it. Or you don't need full stick range ingame and want to use the maximum physical stick range for better precision. There is usually no point using both X and Y at the same time as they cancel each other, except for Y that also sets the max in-game value. Saturation Y and Curvature can both be used to increase precision. Saturation Y will keep movement linear but will prevent you to reach maximum in-game value. Curvature will increase precision near the center then precision will decrease to allow reach max value. As such, it is non-linear. Hope I'm clear :smartass:

Try it, it's pretty obvious. Basically the axis tune options transforms joystick values into in-game values. Saturation Y will limit the maximum value that can be reached in-game. Saturation X will reduce the joystick value requred to reach maximum in-game value. ex: Y 70% means that in-game value will range -70% to 70% X 45% means that maximum in-game value will be reached at 45% of joystick travel. in-game-value = MAX(Curve(joystick-value/saturation-X) * saturation-Y, saturation-Y) Curve(value) transforms the value with constraint that Curve(-1)=-1 and Curve(1)=1

Your example is way exaggerated, it's only about startup sequence. I agree with Az', without INS there's no point doing it now and RAZBAM never said it won't be done.

Quick startup is quite legitimate to ask for, that's a good way to attract newer people. Even if there are only a few switches, it can be intimidating. It can't hurt to have it. I also agree with SkinnyCyclist, I'm not always in the mood for a full startup switchology. Even for people who know the whole procedure, it's quite convenient. Now if you ask about priority, I'd tell you that this feature could be left in the drawer and delivered at the very end, no problem for me :D

That's only true for FR liveries. I have a Canadian livery for example, I can select it only if I set my A/C country to "Canada". Bottom line is you need to use the proper country to be able to select your livery.

This thread is in response to a PM - from this post I made, I guess, although I might have metionned it in another thread: I think it might interest other people, so I write it here instead of answering only by PM. On windows 7 I had this beeping only half of the time, it seemed I had it less often when I would let my computer idling for 1 minute then unplug. However on windows 10 I had this 100% of the time. The only way to unplug the rudder without a painful restart was to shutdown the PC first. There no list of files to remove, I had already tried deleting the USB ports/hubs and reinstalling them (which deletes some inf files, linked to that USB device), with no effect. I didn't find any tool that would work (I think I tried a couple of registry cleanup tools) or that I would trust to fiddle elbow-deep with my registry. What I did is actually a series of back-and-forth from the file system and the windows registry, it's a lengthy process (expect an hour or more), that requires a lot of double checking and a lot af backups: - Write down every string you find into a text file, every string you use as search token too - Do not delete any files, instead, move them to a backup folder - Make an export of every registry entry before deleting it (or maybe only the ones you're not sure about). Make sure you have the time, some coffe and gummybears at hand. Everytime an item was found, I would write down it's name and the ID's it was attached to and every string that seem to be a link to another item. Here is an example of how I proceeded, step by step - bear in mind that the inf file names and CSLIDs (ex: {678DCF40-E2E6-11D5-8CD5-E960089EA00A}) will be different for you. 1- For startup, using notepad++ or any good text editor, search of "saitek" in all windows INF files (also try "mad catz"): ex: C:\Windows\INF\oem31.inf (15 hits) C:\Windows\INF\oem34.inf (3 hits) C:\Windows\System32\DriverStore\FileRepository\sai0764.inf_amd64_6bdaaeadf0069c38\sai0764.inf (3 hits) C:\Windows\System32\DriverStore\FileRepository\saibus.inf_amd64_b55edd864f0ae8f0\saibus.inf (15 hits) C:\Windows\Temp\MadCatz\Pro_Flight_Combat_Rudder_Pedals_7_0_47_1_x64_Drivers\Inf\Pro_Flight_Combat_Rudder_Pedals_Saitek_0764\Sai0764.inf (3 hits) C:\Windows\Temp\MadCatz\Pro_Flight_Combat_Rudder_Pedals_7_0_47_1_x64_Drivers\Inf\SaiBus\saibus.inf (15 hits)2- I open each file and I gather all data and names of interest from them (put that in a text file): oem31.inf {678DCF40-E2E6-11D5-8CD5-E960089EA00A} SaiBus.cat SaiBus.sys SaiMini.sys SaiNtBus SaiClass SaitekMagicBus SaitekMouse SaitekHotKeys SaitekJoystick VID_06A3&PID_5011 VID_06A3&PID_5021 VID_06A3&PID_5041 VID_06A3&PID_5081 SaiMini SaiMini_Service oem34.inf {745a17a0-74d3-11d0-b6fe-00a0c90f57da} Sai0764.cat VID_06A3&PID_0764 VID_06A3&PID_0764 SaiK0764.sys SaiC0764.dll SaiC0764_0402.dll SaiC0764_05.dll SaiC0764_07.dll SaiC0764_09.dll SaiC0764_0A.dll SaiC0764_0C.dll SaiC0764_10.dll SaiC0764_11.dll SaiC0764_12.dll SaiC0764_19.dll SaiK0764.sys {3B0BC249-97F2-49c7-A5B4-8AF34040E48D} {44474645-6B00-4359-B2AE-F94026EA050D} repeat for all .inf files... Note that some files mentioned might belong to Windows, check every file name that doesn't look very "Sai-ish", e.g. WdfCoInstaller.dll or gchand.dll which are actually Windows dlls, you don't need to hunt these ones down. 3- Now I start regedit.exe (as administrator) and I search and note/write every ID that is linked to those entries. You must make use of good judgement to know if an entry shall be deleted or not. Most of the time entries that only link to Sai.. stuff can be deleted, make sure to do backups and check on the internet when doubts arise. To search with regedit, click on the tree root ("Computer"), hit Ctrl+F. After first match, F3 key will show next match. Couple of examples, following oem31.inf in the registry: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/Drivers/SaiBus.sys] This one should be OK to delete, I just copy the path that comes with it in my text file: %SystemRoot%\System32\DriverStore\FileRepository\saibus.inf_amd64_b55edd864f0ae8f0\.\SaiBus.sys [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{678dcf40-e2e6-11d5-8cd5-e960089ea00a}] Doesn't contains much stuff, it's only a repeat of what I found in the .inf file, (class names and GUID), should be OK to delete too.Examples with search of VID_06A3&PID_0764: [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0764] Nothing of interest here, delete. [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0764] This one has link to a CSLID: {44474645-6B00-4359-B2AE-F94026EA050D} I write this down, delete the key, continue (actually that CSLID was already in one of the .inf files).Rince, repeat, search for the names, the CSLIDs, write down what they are linked to, check what's the content of the registry key, again and again. I had some doublts about [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\ROOT\PROGRAMMING_SUPPORT] but it appeared that it was a Saitek-only thing, so I deleted it as well (the entire PROGRAMMING_SUPPORT). Most key and files were quite easy guesses, most of the time you will loop back to strings you already found, you might occasionally find some new CSLIDs, new string (class names, that kind of stuff) and new .inf files. Make sure write the new ones in your text file in a section that reminds you what was the origin of it. Check the [strings] at the end of the inf files to make sure it belongs to Saitek. etc, etc. I admit it's not for the faint or heart :D 4- After this thorough cleanup, I rebooted a couple of times, then I reinstalled the driver for the rudder (I didn't reinstall SST as I had no use for it), and "magic", no more frozen/beeping mouse. Hope this helps, happy cleaning :smartass:

If they manage to apply that foveated rendering to StarVR it will become very interesting!

Very interesting! Despite lower projectile mass and similar muzzle velocity, DEFA-554 is put on par with Gsh-30-1 (pages 7-8 ), this probably due to more explosive portion in DEFA's round as well as higher rate of fire, according to the table page 10. GS-23L is listed too (rated ~2/3 of DEFA).

There is a keybind named "VTB Viewport ON/OFF", using it will bring the VTB on screen as on the screenshots. You need to have a RIGHT_MFCD viewport defined in your monitor configuration (there are default monitor configuration that define it).