HunterICX

I mainly use the L in hard to reach places like when units are hidden in urban areas with lots of clutter that the D might have issues with. When targets are in the open I'd be using the D.

Can't he forward his crash log to you so you can post it here? Just saying you might get a quicker answer that way. Not that I'd be able to help but I've seen developers on this forum pin point a problem with the help of these logs so just throwing that out there.

Might want to put up the dcs crash log so someone like HB might identify the problem.

It's always been like this, the TDC could only be slewed vertically to increase / decrease the range (TDC Range /Pipper Span Control in te control options) in order to grab a target. This is done by the throttle rotator. (see leathernecks Mig21 flight manual) If the whole screen moves that means either something has reset your keybindings turning the ministick into a POV axis.

TDC Range / Pipper Span Control'' should be found under Axis which is the TDC control the 21 has. There should be Button bindings as well to increase and decrease TDC Range. You get any results if you use search in the keybindings menu and search for ''TDC'' ?

I don't really have an issue online*, TWS shots from 30 - 40 nm away for me has a high rate of hit. I don't really babysit Jester aside from the STT,Scan range or A/G stuff. STT however can be a bit of a pain to deal with Jester as he tends to lose the lock rather quick which can be annoying when your sparrow is almost there. *Unless the server is crapping out and lagging bad with rubber banding or planes frozen in place.

Might want to run a repair on DCS, I've had it before in the JF17 and other modules as where I pickled or fired a weapon DCS crashed. It got resolved after doing so.

Wouldn't it be able to make the ''Put Jester through headphones'' a Special Option you can turn on and off? Which would merge the volume sliders if turned off for those who can't use the headphone feature because it all goes through the same soundcard on the motherboard?

It began when they added the feature to put Jester to headphones in the ''DCS 2.5.6.52196'' update from 15/07. before that the ''Hear like in Helmet'' feature worked fine for me too in the Tomcat.

It's never an unsatisfying answer if it helps the issue, I'll get on working on turning of that feature, adjust the volume sliders of the helmet instead and see if I can find a balance so it won't blow my ear drums out :thumbup: Thanks for looking into it and giving me something to work with.

Here they are:

adjusting the volume knobs in the plane like that of the ICS don't affect the Jester Menu background noise when the menu is open. The sounds like that of the Jester Menu, RWR and Radar Alt. are compared to the other sounds in the pit very loud.

Horribly loud Jester Menu/RWR/Radar Alt ETC sound still excists for over 3 updates now. Please make this a top priority because it makes the tomcat awfully unpleasant to fly with it trying to blow my eardrums out.

I was worried when I didn't red in the patch notes it hadn't been fixed and sadly this is now about 3? months an issue that hasn't been fixed. So how long till this horrible issue gets fixed? It's not pleasant at all to fly the Tomcat with the Jester/RWR/Radar Altimeter trying to blow my eardrums out. (and sadly as my headphones are plugged into the soundcard I can't use the temp. fix setting him to the headphones as mentioned above)

Thanks! I'll try that when I get home from work, that way I can enjoy the Cat at least without me jumping out of my chair each time I open the Jester Menu forgetting to lower my volume :D

+1 I would really like to see this fixed, it's basically so annoying and unpleasant that I've grounded the bird for the time being. Is HB aware of this issue? I can't find anyhting where this bug is confirmed and it actually saddens me that it didn't got resolved with the recent update so I'm looking at another month where I'm reluctant to use the Tomcat because of the very unpleasant loud ICS static and RWR sounds.

Can't be a bug if the pylons for the bombs are still a W.I.P

Hi, I'm in need of some help. Doing a livery for a friend of mine he'd like to have a somewhat personalized VF-32 (100) livery. Rather then modifying one that's already made by some of the skin artists here who did an excellent job I'd like to make it from scratch using the template to practice creating liveries on my own. However there's a couple of things I'm finding hard to find. First is the nose art of the F14 100 of the VF-32 Normally for the skins I've made I've had no issues with finding decals or emblems that are either have a transparent background and high resolution or just high resolution allowing me to make the background transparent myself. The above picture is the best I could find when it comes to that nose art. Then there's the ''Deus et Patria'' and the Crew names, can someone tell me what Font is being used? Thank you very much for your time and help you can provide. Kind regards,

simply that's how Vsync works, in case of FPS drops it'll lock it down to the next that's 30fps and because your GPU and CPU don't have to work so hard anymore their usage drop. if you want to cap your FPS use this instead. create a config file .cfg (using notepad++) then make a line as below: options.graphics.maxfps = 60 (you can change the value to anything you like) save it in : Username\Saved Games\DCS\Config

Just make sure you extract as the folder (or create one if it hasn't got one) so it looks like this:

I tried but still can't get a lock using AUTO. made a recording of my attempt

Hi, Trying the 701s they won't lock within 10nm on Auto unless I press the 'lock target' key which isn't how AUTO should work if I'm not mistaken. They should lock themselves as soon they we are in 10nm range after having them slaved onto a target.

I'm on a AMD Vega 64 GPU and I don't have a problem at all with the radar as I stated earlier in this thread, is anyone else with a AMD GPU have the same issue? A couple of friends have the same issue running Nvidia 1050 and 1080.

Login still seems to take a few minutes (last login too 3 - 4 min).