SnapRoll

It's the FC3 ED manual...

In the movie from Falcon it is a closing target. So it should definitely not happen there.

I was only quoting the F-15 manual. The F-15 does not have this problem. It talks about the limitations of the Russian radars. And yes, I would also expect this to happen at a much lower altitude. I am not saying it is all correct. It could be this effect but not quite properly implemented.

Hi It probably has to do with the sidelobe clutter described in the F-15 manual since you are trailing the other aircraft at roughly the same speed. From the F-15 manual: The guard horn is attached to the slotted array in flat-plate radar antennas like the APG-63 and scans together with it for good compensation in all scan directions. In Russian Cassegrain radars like the N019 and N001 however, the guard horn is not attached to the scanning reflector but is rather fixed and aimed in a downward direction. Banking the fighter at low altitude during a radar lock on a fleeing target can thus rotate the compensation horn away from the ground, degrade the sidelobe compensation and break the lock due to ground clutter. During normal scanning operation in search mode, the entire radar Cassegrain antenna housing is roll-stabilized on a rotating gimbal to keep it oriented with the horizon. In this mode, search targets can be lost from the scope if the fighter roll exceeds the limits of the rotating gimbal (110-120 degrees angle of bank). SnapRoll

I wanted to prove the point by doing tests with the F-15 and… I did not expect that. I've set up a mission with a Tu-160 at Mach 2 and my flight path 90degrees to the Tu-160 at the same height. I was basically flying straight with the target on STT lock and waiting until the Steering Dot was centered. This I had to adapt with the F/A-18 a bit since the steering dot is just a tiny bit ahead of the target. All shots were done with the Steering Dot centered and “Shoot” light active. F-15: Steering Dot somewhat ok, but still behind (visible in the AIM-7MH shot) AIM-120C_90deg: corrects to the left and goes straight after the target without lead, looks like it starts leading once pitbull AIM-7MH_90deg: corrects to the right with correct lead to the target. Steering Dot does not show proper lead. F/A-18: The Steering Dot is only a tiny bit ahead of the target. Very visible by the 90deg shot, I was very close to the target by the time the dot was in the center. AIM-120C_45deg: correction to the right, does not have enough lead during flight AIM-7MH_45deg: pulls extreme to the right, does not have enough lead during flight AIM-7MH_90deg: hopeless shot

Hi Guys, can somebody explain to me why the Steering Dot does not show proper lead angle? All missiles pull quite some Gs when coming off the rail, especially when the target's flight path is perpendicular. What am I missing? Cheers

Hi msalama Thanks a lot for your input, I've updated the firmware of my WarBRD and re-calibrated it. This seems to have fixed this issue :thumbup: The center position was a bit offset before. This might influence the return to center when trimming. Cheers!

It started happening one or two updates of the OpenBeta ago. Tiny stick corrections cannot be trimmed out any more. This makes stable forward flight (hands off) quite difficult. It can be easily reproduced when you open the controls indicator.

SimShaker stopped working for me today after the update. It does not have a connection to DSC. Testing Vibe-Motors works fine. Anyone else experiencing this?

I can confirm this, still the same problem.

Hi Chief, thanks for your reply. The whole point was to not have to program anything at all, no matter if the software is equal, better or worse. I just put so much time into my target scripts that I just don't feel like to have to redo everything once again. By the way, I can switch target profiles on the fly without any issues.

Hi VirusAM, thanks for your reply, I was looking for this but could not find anything saying that there is a TARGET compatible firmware for a VirPil base, actually quite the contrary. I know there is a firmware which works perfectly fine with a warthog grip, but it is not TARGET compatible. Can you provide a link? Would be interesting.

I’ve been happily running this setup for a few months now, so I thought I’d share. Like many TMWH users I was also plagued with a sticky gimbal since day one. I’ve done a fair share of polishing and regreasing, but in the end of the day it was all rubbish. I was reluctant to buy a new gimbal and grip because over the years my TARGET scripts evolved quite a bit and I just did not want to redo all the work for all aircraft once again, and I wasn’t even sure if the new software would be capable of similar programming like TARGET. Also, Thrustmaster has given me excellent support (still under warranty) when some of the buttons were dying, so my TMWH was given a life extension. In the end, all I wanted was a TMWH with a high-quality gimbal… This is where VPC came in… I ordered a VPC WarBRD, an extension set, and two TableMounts once they were finally available. First off, as expected, the quality of VPC products is excellent and I can recommend it highly! My little mod was to drill a hole in the 9cm VPC extension and solder an 2m extension cable for the Warthog Grip so I could use the WarBRD gimbal but plug the grip directly into its original base which is standing behind my screen. Pros: + TARGET software can be used without any limitations like before + Butter smooth center and travel + Angled grip position for ergonomics + No binding of WH-Grip and table mount when using WarBRD and the 9cm (10cm) extension + No problem for the stick to return to center from any position - no curved extension needed + No special machinery needed for the mod Cons: - The stick wobbles in the center when let go, but this is to be expected without dampening. For those who are interested in using an extension, it is important to note that you have to untie the 4 screws connecting the vertical table mount arm and the gimbal mount arm so it can settle a few degrees downwards before you tighten them again. This will give you enough room between the grip (button) and the top of the table mount. The wobble in the center is absolutely no problem since no one will let the stick just go. The only time I’ve seen negative effects so far is, when I was flying the Su-27 supersonic, hands off and on auto pilot and at the same time pumped into the stick. This would induce some oscillations. Other than that, there is absolutely no problem flying hands off in planes or helis with or without auto pilot. SnapRoll

I just flew Mission 10, but other missions seem to be affected too. FARP Otkritka does not send any ARK-UD signal. Also preset channel #4 on R-282 does not point to Fort-4. Can anyone confirm this issue?

I got a Samsung U32E850R @4k with a GTX1080. I enabled it for full screen mode only, but windows and full screen works too. It is easier to determine in which mode you currently are when you keep LAlt-Enter-ing when it works only for full screen. Freesync does work for me with both Samsung Freesync Settings “Standard Engine (50Hz-60Hz)” and “Ultimate Engine (40Hz-60Hz)”. What is strange tough, after rebooting the PC and starting DCS, I get heavy jittering, but once switching from Standard and back to Ultimate, all works perfectly fine. This does also happen the other way around when booting with Standard. Since I run it at 4k with a normal 1080, there is not much head room when the screen can only clock down to 40Hz, but I must say it gives a much smother experience. Fly close to the ground over a forest, look 90 degrees to the side and move your wings up and down so you transition from trees to sky and back. The difference with enabled and disabled is remarkable. Will see if I will be happy with this in the long term…

Hi Does anyone know how to get the rest of the total 8 Mustangs into the air in Mission 6? My wingman crashes on takeoff and the rest just stays on the ground. This is probably connected to the wingman-crash-on-takeoff problem but maybe somebody figured out a way to get the rest of the flight in the air. Cheers

With the TARGET GUI or script you can just define a button press (key combination) depending on the position of the lever. Are you actually using TARGET?

Strange DDI switch off behavior I’ve just landed in the case1 landing instant mission and noticed some strange DDI switch off/on behavior. It looks like a bug to me, but maybe somebody knows better. I switched off the left DDI first and then the right. For some reason, the HUD and the AMPCD also turned black after switching off the right DDI. Then I turned on the right DDI again, only the HUD came back with it. Then after switching on the left DDI again, the AMPCD came back too. (I did not switch of anything before that, so the engines and generators were online) Are they in any way linked together? Seems odd.

I just noticed some lightning issues in today’s update. I’m not sure if some of them where there before. The sun shines through the instruments and mirror, and the sun visor is of no use. Also the cockpit lights seem to have become much weaker. The last to pix show it off and on.

It says to press the FCS BIT test button on the right DDI while simultaneously holding the FCS BIT Test switch on the right wall in the on position. I’ve noticed it works just as well if you first press the DDI button and then the FCS BIT Test switch on the right wall. One after the other, not at the same time (mouse). Don’t know if it is supposed to work like this…

sounds like a DNS problem... What do you get when you do "nslookup www.digitalcombatsimulator.com" on the command prompt?

27 fps @4k I got 27 fps @4k, but right after take off I get 60 fps (V-Sync on) It very much seems to be a CPU bottleneck. My GPU is @50% while one CPU core is kind of maxed out. I fiddled around with the graphics settings a bit but none made any difference. i7-6850K @4.13 (HT off) 64GB RAM GTX1080 (8GB) Samsung SSD 950 PRO NVMe 4K @60Hz Monitor FXAA enabled in NV control panel Since performance is very much FOV dependent, here my settings. See also attached pictures. [13] = {--default view viewAngle = 107.257050,--FOV hAngle = 0.000000, vAngle = -13.296885, x_trans = 0.130000, y_trans = -0.008300, z_trans = 0.000000, rollAngle = 0.000000, },

I might have pulled the second wire a bit too much :-)

Mission 11 SEAD strike hardly ever gets its job done Su-25 illuminating the battlefield, but it is daylight Some of the armored vehicles are inside the woods, but they can be hit I was able to finish this mission but it was hard since the data link is not working at the moment Mission 12 I cannot get this one done. The bunkers and their defenses are hidden inside the forest and cannot be hit. The two Mi-28 are not of any help since they cannot find any targets.

Tried the "intercept" instant mission for the Mig-15, and then also tested with Mig-29 and Su-27. The bullets just go through without damage. Could not even get the Mig-15 collide with it in the air. Anyone else having this problem?