Sadist_Cain

What devilry is this?! I am most intrigued, any chance of a vid?

Vent? xD That's just the way it is my dear fellow that's not venting lol apologies if the bluntness is abrasive to you. I don't agree that it's acceptable that it's still in this state, players shouldn't have to work around and suspend disbelief to this extent still when trying to use the harrier systems as they're intended to be used. So by that measure of course I find fault with a video detailing a broken/half implemented system as ones own "version" of doing things. I'm pleased for you that you're still entertained with the current state of the Harrier and happy that you've crafted your own world of fun for yourself with how it is at the moment. We shall both look forward to the rest of the features I'm sure. :thumbup:

You can absolutely restart an engine after a fire, not supposed to 9/10 times but you absolutely can. Sometimes you get restarts where the engine blows itself out and can't sustain it's combustion, usually after a few rinse and repeats you can get it spinning back up with ~40%-70% of its power. Much much easier to do with split throttles as there's less juggling of throttle modifiers. I get truly baffled when I see folk, even prominent youtubers saying they've never managed a restart in the A-10C. Honestly I've lost count of the amount of times I've restarted an engine in flight, not everytime I grant you but more often than not I'm confident in getting an engine fired back up after a hit.

The issue comes with the fact you're making excuses that do not need making for an incomplete module simply because you're indulging your Brit in the Falklands fantasy with it. It's fine for you that you're immersed and entertain yourself with pretending like you're in a Sea Harrier, the ire comes when defending very poor conduct simply because you don't like the reality poking in the fantasy bubble that you've created for yourself around a half baked module. These are work arounds for incomplete and/or broken systems that should be working by now, the fact you or anyone would be making 'tutorial' videos on how to work around missing features is in no way a positive thing. We're all doing stuff, the difference is we're a bit fed up with the bodgejobs and have moved passed the point of being amused by them whilst you're still finding them so novel. We want the stuff it could be doing and how it should be doing it and these hacks just highlight the missing capabilities of the aircraft that we should have by now. You may well be satisfied with spending 50-60 odd on an AV8B Harrier module in order to just stick an RAF skin on and pretend like you're fighting Argentinians the 80's, most are not. You may well be enjoying playing in the box that the Harrier came in, it's a great box, you have a marvellous imagination and that's great. That doesn't mean everyone else who bought an AV8B should be satisfied with just the box, or should be happy that they can stick an RAF roundel on it and call it a day. People want the Aircraft they paid for, not to be fannying around with half mile inaccuracies and missing range cues, borked ASL lines, non-existent loft profiles, broken radios, missing CAS pages, incomplete navigation, broken-fixed-broken features, sidearm volumes etc. etc. Especially after this long.

Useful technique where several hundred feet margin of error is acceptable :thumbup: In all seriousness though I've been doing this bodge CCRP toss bombing for quite a some time seeing as it's the only option giving the glacial rate of progress to getting the actual loft bombing profile. It's pretty much useless with iron bombs unless it's a VERY specific circumstance (i.e. no wind and a loooooong convoy conveniently on a bridge) and even then there's always a much much better way to go about destroying the target. LGB lobbing is a good laugh and great if your target is behind a ridge with a JTAC involved or a buddy lase who's above the target threat envelope. You just need speed over 500 and a pull up from 4-5 mile away, nothing technical to it. Doesn't make up for the fact we have no functioning loft bombing profile... still :P

Tough :P :joystick:

the accent of whoever set up the profile shouldn't have any bearing on the quality of the voice recognition. *sometimes* phonetic spelling may be used on tricky words but the overwhelmingly vast majority of terms are just text that's read by the computer, it's up to your own voice recognition profile in windows and how well you've trained it which determines how well the voice will be recognised. Ultimately it doesn't matter if the person typed "Engage" is german, southern drawl or welsh it's your own windows profile that decides how to listen for it. There's the standard Voice recognition training built into windows, "The computer is learning the sound of my voice as I speak" etc. etc. this builds up a general profile for the way you speak to establish a good baseline. There is a massive difference between using a trained and untrained profile, untrained is practically unusable for most. There is also a training mode built into vaicom, it is detailed better in the manual and the instructional video but the jist is that it will turn on windows voice recognition software itself (normally used for dictation and the like) and it will then highlight each word in the Vaicom dictionary and listen for how you say it, then move on to the next one until you have built up a dictionary of each specific term, to further enhance the accuracy.

Same here, laser code and radio frequencies, bashing the enter key a couple of times or double tapping the key to input the data in the first place can sometimes help.

Should be I think, just not modeled at the moment. As for the conversion I have a hill billy mad math method that agrees with my mind parts seeing as I ain't no mathematrickster. 054°14.768 Take the first decimal, multiply by 6 So 7 x 6 = 42 Then round up/down the second decimal, whichever is closest. .768 > .770 To be 'exact' you're dividing the second decimal by 1.6 but eyeballing it is fine e.g. you would add 3 seconds if the second decimal was 5, adding up to 6 additional seconds total. In this case I'm adding 4 seconds. (7 / 1.6 = 4.3ish so 4 will do) 42 + 4 = 46 So my 054°14.768 becomes 054°14'46" It's filthy and bizarre but I find it really easy to do in my head quickly and it somehow spits out reasonable numbers, gets the job done.

Point track no worky in CCD mode iirc. As the chap said what is most likely here is that an aperture on the TGP was masked rather than the one you were looking through. We can see that your TGP is on your right wing station and the target is behind you and left, so it's likely that it's obscured by the rocket pods loaded on the next station. How to solve this? think about your flying and your angles, maybe if you were at 12,000 instead of 8,000 the slant would have the TGP unobscured? You *could* turn left and fly level which would get the target into view quicker however it would become masked again quickly and become more awkward to deal with. In this situation I would climb to a higher altitude if possible, between 10-12 like I said and I would go about getting into a right hand orbit around the target area. With the right wing dipping the TGP below the aircraft there is very little in the way of obstruction and with careful flying whilst being aware of where you are and where the TGP is pointing you could maintain almost unbroken LOS on a target area indefinitely.

:music_whistling: Visor helps you see at night too... Not that it should :doh:

Different problem here, can't get TACAN to turn on. trying to mash this script into through the Infero which is working fine barr two issues. *Solved* Firstly the TACAN, I changed it to be a trigger as described but simply can't get it to turn on. *Solved* Secondly, probably nothing to do with this script but thought I'd try my luck anyhow, the F10 menu loses everything except for JTAC target reports for everyone except the host. I think this is TTI related as it does that whenever I add a new ship so no worries about this but if anyone might be able to help it would be appreciated. edit: Fixed the first problem, I hadn't set up the waypoint and trigger zone properly

Strangely enough RAZBAM themselves have done the growl in FSX. Can't understand why the version we have is lacking. I still hold out hope Diveplane will return and finish his harrier mod :)

Vaicom 2.0 is the only way to do voice control in DCS, everything else pales by comparison to what you get out of the box, even experienced VA folks would benefit from using it as a starting point. Hollywood is a top notch fellow as well and supports his product very closely, he's helped me personally with many an issue and certainly listens to his customers on ways to improve. I bitched about 'muh immersion' for the link to radio power for chatter, days later there was a setting in Vaicom for exactly that. Cannot sing its praises enough, Vaicom Pro all the way. Have you tried downloading Operation Bactria for the A-10C and running that with VA? it's fantastic, the level of JTAC interaction, theme and setting of the mission all come together brilliantly to make a marvellous experience.

Thank christ for that.

Get inventive with a brake cylinder or other hydraulic doohickery, as flagrum said FFB will only go to the stick 99.99% of the time, so any kind of mechanical feel you can get plus a potentiometer or hall sensor stuck on to it will be your best bet

HUD Reject modes work. I like REJ1, changes the FPM and AOA from numbers to a graphical representation.

If I may clarify somewhat here... He's not referring to the Parking Brake (although that will prevent you from aligning the aircraft if it is off) but more the "throttle cut off lever". It's an awkward little switch that resides around your pinky on the throttle handle, it happens to sit very close to the parking brake lever and you may need to use the Flashlight to see it properly or rotate your floodlights. (Ctrl + L or Alt + L for the flashlight, something like that) You can push the throttle from off into idle by pushing it forward but to reset it you need to lift up the lever, it's akin to the detents found on the A-10C just witch a reset switch instead of a detent. So to start up you should see the RPM counter rise to 9.2% and hold there then when you bump the throttle forward, pushing it into idle, the rpm should climb to their idle point around 28.5 or something there. If you do not see the RPM move from 0.0 then the most likely reason is the throttle is not in the cut off position, just click the lever (or bind it to a control) and you'll see the rpm rise as it should to 9.2 where you can then bump the throttle forward as normal.

Same here, using with Vaicom so Radio issues tend to become irritating rather rapidly

Use CLEYE for your drivers. For the visible light filter either grab some floppy disks, exposed film negative or even 3d glasses lenses and that can act as a filter, layer that in front of the camera and fiddle settings until you only get your trackclip LEDs showing up. Be sure your cameras physical zoom is set to the wider FOV 75° (the blue dot). Some PS3Eyes have an easily removal IR filter, google instructions and model numbers to look out for, don't worry if yours isn't removable as it'll still work very well. Best of luck with the journey dude, absolutely welcome to PM me if you have any troubles.

Same problem here, hope this helps. 99% of the time the game crashes without a crashlog, just straight to desktop, this was that one time out of a hundred it spat something out. Loaded up the mission and collectively spammed my way through the F1, F2, F9 and F10 keys, game crashed less than 10 seconds later. All mods removed DCS Cleanup and Repair install. Nvidia drivers uninstalled with DDU, 419.71 installed. Repeated the same steps and still crashes. dcs.log-20190129-183902.zip

Alienware AW3418DW here, absolutely phenomenal. Features like Gsync or freesync, high refresh rate and high resolution are not to be understated at all. My motherboard blew out a while ago and I played on the 50" 60Hz 1080p Plasma TV and it felt awful by comparison, couldn't read anything, nothing felt smooth. I haven't seen a tear since I got this thing, everything else feels broken by comparison. When it comes down to DCS, in particular the AV8B, the added spatial awareness is great, the fuel basket goes out of sight as it's just about to pass by my left shoulder, spotting for the landing transition to the carrier is less blinkered, I can still read everything whilst leaning back and looking around in general is a whole lot less disorientating. The curve completely draws you in, you don't notice it as a curve per se just the sensation that you wish to lean forward and crawl inside the screen. Outside of DCS general productivity is awesome, I don't bother with full screen browsing anymore I just chuck it off to one half of the screen and use the other half for something else happily not feeling cluttered at all, text based applications can be reduced to a quarter of the screen yet still have the presence they would in fullscreen on a laptop. Can't recommend them enough.

Explains the off putting nose high feeling I get when landing, good spot.

Flight simming in general Highly recommends head tracking for the past decade. I personally would never bother with Trackir, just get a PS3eye camera (grabbed a handful for 50P each from my local GAME shop) grab a trackclip pro or make one if you're so inclined. Download Opentrack for free, have a few headaches(Less than TIR) and boom you're there, up and running for 30 quid or less, no reason not to. True, my buddy flew the huey and the A-10 for a while with an XBox Controller, he did buy TrackIR first though so that shows the priorities. You don't need headtracking, nor a joystick or anything to 'enjoy' thelevel of simulation on your own terms. You do need those things to fulfil the potential enjoyment you can yield from the increase in ability and competence these devices afford you. Whilst better joysticks, rudder pedals and other input devices might aid you in flying more smoothly or operating the HOTAS systems and other functions more efficiently and with more fluidity NOTHING compares with the benefits of head tracking. You gain situational awareness, the ability to operate switches and systems easier and quicker, you gain the use of a hand or other controls that were otherwise bound to view commands which in turn will improve your flying whether on a keyboard or a warthog. You're offloading the most important and most used commands (looking) equal to or more important than to flight control to a new control system that is the naturally intuitive option. Whilst not needed per se, whether you use VR, Eye Tracking, or Headtracking it is certainly essential to enjoying the sim or any sim, to its fullest

For science I'd be curious how much trim it takes to achieve level flight with the configuration you mention, whether the aileron is halfway through its range of motion or not.