paeagle

I think this is a very individual matter. A setting that seems to be great to one person may be hard to accept for another. But just spend one evening with testing and you will find what suits you. I have installed AviaSim - Soft Center cam profiles and light springs in my T-50CM2 base. This is my "jets" configuration (75 mm extension) ... This is "propeller / helis" configuration (75 mm + 100 mm extensions, the base shifted down) ... Both are very good for my old shaky hands.

Marianas map is great with all its details, thanks DCS for it. I took a short morning walk in the area you mention, I also looked at the lying bike. FPS score (75 in DCS counter / 88 in AMD performance tab) seems to be pretty good for me there - see the attached screenshot.

I have separated UP and DOWD positions of these switches using four new lines added into ... \Mods\aircraft\AJS37\Input\keyboard\default.lua. Look at the attached file. default.lua

I have been using the same hardware combination as it is described in the title of this thread since the end of last week. I also use TARGET, so I had the same problem with POV when I connected new stick to PC first time. I found good advice how to solve it here ... https://forum.virpil.com/index.php?/topic/2885-new-firmware-problems-with-thrustmaster-target-script/ I replaced current version of Virpil software with this one yesterday ... https://support.virpil.com/en/support/solutions/articles/47001125308-vpc-software-setup-20200325- The problem has been fixed, no new one has appeared. Everything works as with the original TM base, I didn't have to change anything in TARGET profiles or in the settings in DCS. This thread is two months old, you have probably found some solution already, but maybe this information will be useful for someone.

The same issue. It is impossible to set a course line position precisely using the course setting switch with this bug. At the same time, we have another bug here ... https://forums.eagle.ru/topic/256639-course-switch-keybindings-produce-non-stop-course-input/ ... so this feature has been corrupted during last updates.

I don't want to start any fight :) , but I would say that Harrier is quite usable for night operations in current OB. See the screenshots below please.

My settings for the flaps on A-10C is shown in the pictures below (no key command is set for FLAPM switch position) ... This way I get adequate switch position for each separate flaps position (up, maneuver - takeoff, down). It is only needed to check and if necesarry to synchronize the switch and the flaps position during the startup procedure. Than it works correctly until I leave the plane.

Broken catapults on Stennis I tried to take off in MP with Hornet from No. 1 catapult on Stennis, it didn'work, so I moved to No. 4 and took off from there. That one looked to be OK. I landed succesfully on the carrier in the end of the mission and then after refueling and rearming I wanted to take off from No. 4 catapult again. I was aligned with the shuttle, the launch bar was extended, but instead of a hooking the bar with the shuttle, the plane was thrown up when I pressed "U" to hook the bar. Hornet flew across the deck and fell into the water. This accident happened to me twice after the 2.5.6 update, never before that. Short video captured from Tacview record is attached. DCS track file is too large, it's about 100 MB and not quite correct. I tried to replay it to make some video or screenshots, but the flight ended in a crash after about 30 minutes in the record, the landing and the second taking off from the carrier was not there. Stennis_Cat4.zip

The bomb sight behavior seems to vary depending on a map. Three tracks from simple tests are attached below, I tried to repeat the same dive attack from about 2200 m on different maps. Caucasus: The sight first moves down and right and then skips to center of the HUD. It is little bit confusing but there's enough time left for aiming. Persian Gulf: The sight appears just in the center position after the start of the descent, but somewhat later, I would say. But I am able hit the target. Nevada: The sight appears on the HUD too late for me. Viggen_Dive_Bomb_Caucasus.trk Viggen_Dive_Bomb_PG.trk Viggen_Dive_Bomb_Nevada.trk

I use Thrustmater MFD frames together with Warthog stick and throttle and I assign functions to all these devices using T.A.R.G.E.T. All function mapable on a keyboard can be easy assigned to the rockers on the MFD frames this way.

The changes shown in the screenshots above were implemented in the stable version last week :-) . See DCS 2.5.2.19682 Update 7 in this thread ... https://forums.eagle.ru/showthread.php?t=214251

Todays changelog (marked as DCS 2.5.2.20036 Update 8 in DCS World 2.5 Changelog and Updates of Open Beta section) is almost the same for Viggen as it was two weeks ago (DCS 2.5.2.19641 Open Beta Update 7). Is it mistake?

Yes, editing of waypoints via cursor on the moving map in North-Up position is uncomfortable now. But there are also other issues associated with changing of the map orientation. As it is shown in the pictures below, some symbols move incorrectly when the map is switched to the North-Up position. Notice how the TACAN bearing pointer moves in the first picture ... And here's the waypoint position change (WP1 coordinates were entered using the UFC keypad).

It seems that this Viggen module problem has not been resolved yet. The log file is attached. dcs.log-20180707-062747.zip

New function of the moving map is great but the response to the commands is somewhat inconsistent. When I move the control stick left the waypoint moves left on the map (and vice versa). But when I move the stick up, the waypoint moves on the map down, so behavior in horizontal and vertical direction is different. And another note. The NOSE UP map mode is preferred for this new function. Even if I switch the map to the NORTH UP mode, the relative direction of movement of the waypoint / the map stays the same. Maybe it would be better to prefer the NORTH UP mode to edit waypoint position.