Laithar

Good to know, I changed it to digital TDC and was able to slew with a smoother action. Thank you for this. Yes, I didn't use the same words but did mention this in my original post. Thank you for your reply though. I admit, the first couple of times I did not but after some youtube video tutorials, I corrected this and there were explosions on the ground. Thank you for your input. Hope so. I think what I find most frustrating is that I watch videos to get an idea of how to do things and then I'm not able to repeat it. So I check the video again and still I'm not able to do it. Then I find out that things have changed and so the old tutorials are not relevant any more. Thank you for your reply. Unfortunately, a lot of the tutorials are out of date already. Thank you for your input. Yes, I had watched a video explaining this. Thank you for your reply.

Hey guys Hope you're having a marvelously better day than I am. Haven't been on the Harrier for a little while because of the release of the Hornet, however I do like to keep practicing my laser guided A/G bombing runs. I've set up a little mission where four AAA units are moving along the road and although I know roughly where they'll be, it gives me some spotting xp because it's never the same place twice. Originally, I was bombing them using the Warthog from around 10,000ft using GBU-12 or Mavericks and everything worked flawlessly however when I tried with the Harrier, things became a little frustrating. I loaded the Harrier with a TPOD and six GBU-12s, took off and headed towards the area where the AAA units are. Once spotted, I flew about 10 miles from the area, turned around and pointed the nose of the Harrier towards the general area and proceeded to slew the TPOD using the analogue TDC control on the Warthof Throttle (I did have the TDC button selected on the TPOD screen and the throttle slew control has been upgraded). It did not want to move, yet in the A10-C it was perfect. I tried again and it moved but then stopped. This became the normal operation that it would move a little and then stop dead. Eventually, I got slewed to the target and pressed point track mode. Again, it wouldn't change from area track mode. I tried again and again but no joy. I flew over the target having not selected it and turned around. I irratically slewed onto the target and pressed point track numerous times and eventually it changed. It locked onto the target and stayed following it. I pickled my bomb but no shack! Then I remembered from a while back something about having to update the DMT target information otherwise the bomb won't see the laser to follow it, don't know if that has been fixed so I tried again. As I approached the target I slewed the TPOD again to update the info and it went into area track mode again and I couldn't get it back into point track mode until after I had flown over the target. This whole scenario keeps happening. I love this module and know it is in EA. It doesn't bother me the slightest if it is bugged but I am sure I was able to hit targets with GBU-12s and Mavericks before and slewing wasn't a problem either so what am I doing wrong now? I just can't figure it out. Any ideas? Cheers

Is it possible to change my forum username to reflect my callsign. I've checked in the list of members and it hasn't been used. Or do I have to start again and re-register? Thank you

Thanks for the reply Hollywood. I removed the VCOM PRO blocks as requested and restarted VA but it made no difference. Then I noticed the Export.lua had a block from version 2.5.3. Removed and everything is working wonderful again. Thank You!!!

@Hollywood Yes, that is what I've been doing since I got VAICOM but now it's not working. I didn't know if I'd unknowingly turned off another setting. I say 'Batumi', voice attack beeps to tell me it requires additional input then I say 'inbound' and voice attack marries the two together and gives a beep at a different pitch to say accepted. The voice attack shows as follows: Joystick: 'Transmit TX2 press' Listening resumed Recognized:'batumi' (Confidence 90) (awaiting additional input) Recognized: 'inbound' (Confidence 88( TX2 | UHF: [batumi],[ ],[ ] Inbound [ ][ ] Joystick: 'Transmit TX2 release' Edit: Just noticed despite DCS showing Easy Comms off, the green screen of the VAICOM plugin is saying it's ON. Toggling Easy Comms in DCS makes no difference to the VAICOM display

I've turned easy comms off so that I have to select the correct radio frequency and for some reason, I kind of expected that if I select 131.000MHz for Batumi ATC, I would automatically be connected to Batumi ATC. However, when I say 'Batumi, inbound', it doesn't appear to work that way. It recognises the command with a confidence of 96-98 but if there is an airport or farp closer on a different frequency, communications seem to be directed to that radio station instead. So I say, 'Batumi, inbound' and the comms is repeated as PLAYER: Dallas, Colt1-1, inbound'. When I look in the comms menu, I notice it is occupied by the 10 closest radio stations and Dallas occupies F1 so if I want to communicate with Batumi and it's on F4, I have to use the menu. This breaks immersion for me and defeats the purpose of Vaicom. Does anyone know if there is a way to stop this happening?

Thought you would at least ask for M&M's sorted into their respective colours. Fresh fruit is not very 'rock 'n' roll...:lol::lol:

To make things clear, I never normally take off with flaps up. I did it to test what would happen. I expected to go into the drink but it did the opposite and acted like it had flaps full and a half or something so no user error...it was done on purpose. Thank you to aaron886 for making the bug known to me.

What would you expect the plane to do if you took off from the cat with no flaps set? Try it! My plane starts a vertical climb and goes into a loop. As I try to rescue her by pushing the stick fully forward, I don't have full control. I try pushing the stick forward to stop her from climbing but she's stubborn. The best option for me is to roll her at the top of the climb and by this time she's lost speed so takes a dive. I could imagine this would be quite frightening if this happened IRL. I realise most of this happens before the flight control system actually takes control but if I manage to get her above 250 knots, I still have to fight the stick. It's not until I come below 250 knots, drop the flaps, raise them again and take her above 250 knots again...that I gain full control.

Yes, something has changed. I now struggle to keep the nose down on full mil power if I bolter and never need afterburner off the deck. It's the same with takeoff from the cats...I trim to 15 and only use half flaps. I have to lift the gear and raise the flaps as soon as I leave the deck otherwise I'm hitting 30-40 degrees quite rapidly. The nose dips a little without flaps but until the flight control system kicks in at 240-250 knots, I'm fighting it. Same after the break for recovery. If my wings are straight and level at 250 knots and I drop the gear and flaps, my attempts at staying at 600 ft are impossible as I push the stick forward to fight the nose rising to between 800 - 1000 ft. I don't see any of that in the carrier break videos on youtube. Anticipating the nose dropping and applying throttle isn't any easier but once the correct AoA is achieved, the rest of the landing is a doddle. Trouble is, by the time I've got the correct AoA, the carrier is way into the distance and I'm long in the groove. It wasn't perfect before the update but my carrier landings were okay. Now it seems like a different beast.

I use a 4k monitor but DCS resolution is set to 3840 X 1440. It runs okay at straight 4k but as was mentioned previously, spotting is easier on the lower resolution. I also have a 1080p screen attached to the same GPU, which is a standard GTX 1080. I don't see any problems with frame rates. When the new nVidia GPUs are released, I'm crossing over to VR. Also looking forward to the Vulkan API being introduced as I have a 12 core machine. Krazee S!

I used to struggle with AAR but things are a little easier now that I experimented with the curves on the joystick. I found that there was a huge wobble with the pitch, the up and down motion seemed to be huge so I dialled in a curve of 25. The rolling motion doesn't need so much so I only dialled in about 18 or so. The curves slow the response down just enough although the plane can still throw a wobble every now and then if you're not concentrating. Persistant practice makes perfect. I could dial in more curve and make the joystick even less sensitive but then the joystick doesn't feel connected so much and the hornet feels sluggish. I think it's just a case of experimenting. I can even refuel off of the S3 now and keep up when it banks, which was always more of a challenge than the others tankers for me. As far as trimming is concerned...in the hornet, I think the flight control computer counteracts any trim you try to put in. I've tried trimming and it doesn't seem to make any difference unless you're travelling below 250 knots, which is when the flight control system 'relaxes' it's control. I have refuelled to max without losing connection and the flight control system seems to keep it steady despite the extra weight from the fuel. Hope this is helpful. Krazee S!

My problem is with opening the configuration window. It looks like it's open if you hover on the voice attack menu bar icon but it shows completely white and no window is open on the desktop either. I tried reinstalling voice attack, which is version 1.7.2; reinstalled Vaicom Pro, which is the latest download and deleted the lua file but still no joy. Any ideas?

Since the seventies, I've enjoyed flying various simulations on various computers built by Commodore and then finally migrating to the PC. When I first bought DCS World, I had a feeling it was going to be the biggest and best to date and Eagle Dynamics have not disappointed. I love the A10-C, AV8B and now the F/A18-C (I even enjoy flitting around in the Huey). I'm more interested in the flying than blowing things up and shooting things down and for that alone I am well happy with the simulation. That said, whenever I find a problem, despite knowing things are in early access and are continuously being developed, I trawl through the forums to see if I can find an answer. I often hope that it is an easy fix but that's not always the case. With regard to draw distances, I have everything turned up to max but still distant objects seem to pop out of nowhere. I'm sure many of you are aware of the problem. It doesn't seem to matter whether I am using a 4k setting or tune the screen down to 1080, objects seem to be hidden behind an invisiblity cloak until you get a certain distance away and then bam, they are as large as life in front of you. Case in point, the thick black plume of smoke emanating from the Tarawa. As you fly towards the Tarawa using TACAN as a guide, there is no gradual fade in...it just appears. Obviously this happens with trees and buildings too as they have a tendency to grow out of the ground quite rapidly. And I guess it is what governs spotting targets too, to a degree. I can zoom in and they appear sooner, which seems to suggest that the draw distance is zoomed too but relying on zoom is not the way to go as that introduces the necessity to keep your head completely still or have TrackIR view bounce all over the screen especially if what you are looking at is not central on the screen. I also notice that if using a targeting pod or such like, I can see further into the distance and there is a definite 'fog' where beyond the line you see scenery but no ground objects and as the line moves in the the general direction of the aircraft, objects pop in and out of view instantly. I realise that sometimes, to get software to run on certain computers, decisions have to be made to 'tone' down certain settings but I consider myself lucky in that I have a very powerful computer with a decent amount of RAM so I wonder if there is a setting hidden in a lua file somewhere that governs the draw distance so that I can see things from further away? Something that will move that fog line further into the distance or eliminate altogether? At the very least it would be nice to be able to see objects smaller so that there is more of a gradual introduction.

I agree, I don't think this banding is right either. Whereas the whole back glass used to make it a darker shade, this is a definite band that gets wider/thinner depending on the POV. This dark band only affects the front glass as I see it (Banding 1.jpg). It gets thinner the higher you sit in the seat (Banding 2.jpg). As the POV changes, it also starts to affect the graphics that are projected on the front glass, making them illegible (Banding 3.jpg) and that destructive band, (which appears to be clear at the bottom of the back glass), becomes wider so affecting more of the graphic on the screen (Banding 4.jpg).