Dingo_Bob

Zeus mentioned it in another thread that they are not compatible as the BIN files are assigned to each version and are not the same, he did also say you can copy them and remove the bin file but that would most likely break some if not all functionality in the cockpit and controls

it's a fickle business, and lots of grey areas, but I don't see how anyone could stop you bashing out a free digital representation of something on copyright grounds, when IRL you can go out and find and bash out a load of scrap metal and build a perfect working & flyable example of an aircraft and then put said aircraft up for sale with no issues what so ever [ame]https://www.youtube.com/watch?v=mOz7fmuvabI[/ame]

they do work but can be buggy, also since 1.5 the AI models now have a hard set cockpit that can't be removed for the human one so you get a duplicate cockpit the human one and the low res AI one, similar with flyable plane mods, these can be corrected slightly by moving the pit location up down or forwards, but in the helo's you are limited by the rotor blades height and them intersecting the roof of the pit if you move it up

Come on already!!!!!!

yes you need to have an idea of where the target is and which direct ion the laser is coming from, but you don't actually need to "bug the target with the pipper", you can release the GBU from any height, early enough with enough inertia for it to travel to target or at a slight dive angel / bomb fall trajectory that it'll pick up the laser on it's flight to the target area as in below I know the targets are on the Damn and that the AH-64 is lasing from somewhere north east of the inlet into the damn, so I try to line up my release in the general direction of the damn and along the path of the laser The second release sort of proves the theory, that the bomb can't find the laser if it's released at too far an angle from the direction the laser is pointing [ame] [/ame]

Wonder if Leatherneck can wrangle Michael Ironside into doing the voiceovers for Jester, that would be awesome :D, and only have him available in the Tomcat and Skyhawk (if one gets built :D) have someone else random for other aircraft

yeah 150 - 200 meters works, it becomes a bit more hit and miss the further away it gets, but too close and you stand the chance of the JTAC getting taken out by the exploding target / GBU impact

Ok you Have several JTAC setup Most are too far from target groups to lase, and the one named from pic above JTAC (Axeman) is in a starting position facing away from the group you want him to target also it might be too far away 800m across a road and a ditch so there is most likely a line of sight issue for it

it should, work as it should for me, maybe try a repair if you hover over modules if pointer changes to finger then its not installed if it stays a pointer then it is installed

I'd say 2.0 only needs a terrain in the correct location to run, and since you can now (with some JSGME jiggery pokerie) import Caucasus now it'll run as there is a terrain in the folder for it to load.

you still use real cash it's 2016 what's that like :D

the script tells you all the same info as regular JTAC so not really cheating, you just loose the need to call laser on, ip inbound etc, The normal JTAC is just a bit more fussy to get him into a position to lase he has to be super close, but the GBU will travel to the laser from any height once you aproach from the right direction and it's visible to GBU's receiver, so no need to use the piper/cross hair, so same would apply for human JTAC, you could be talked onto target by buddy and drop from Height in a similar way, not sure for Humans in the Russian aircraft as I think the laser codes would be different, the script should work for the AI though as you set the laser code in the script.

Tacview of above, GBU's released no target spot applied with piper/cross, AFAC Apache is Lazing, GBU released @ ~20000' & 8Km off target, GBU acquires laser and glided to target Mission is here cheers Xaoslaad, saved me the hassle of working it out :D http://forums.eagle.ru/showpost.php?p=2671232&postcount=50 [ame] [/ame] Tacview of below video https://www.dropbox.com/s/49oo4nwojq4f72w/Tacview-20160217-213849-DCS.txt.acmi?dl=0 [ame] [/ame]

So if I'm reading the update right this update is for 1.5OB and brings it on par with what 2.0.1OA got last week except 1.5OB now has L-39ZA?? 1.5 release unchanged as yet

thought I'd add this here too just to highlight it :D no need to use the target cross with laser using CTLD script, GBU's follow laser once they can see it, more testing needed to see if normal AI JTAC / Human laser behaves the same I'll post a track / tacview later when back at the PC, but have been dropping from 25000'+ at 7Km+ out from targets and getting laser pick up and target hits every time http://forums.eagle.ru/showpost.php?p=2680512&postcount=63

handy page for conversions http://www.hochwarth.com/misc/AviationCalculator.html I think iirc you multiply the QFE inHg by 33.86 or 33.87 to get mbar so 26.76*33.87= 906mbar?

Nice utility Skate, how'd I miss that must be going blind :D

make sure Tacview is pointing to the correct DCS install folder, it defaults to C:\programfles...... so if you have it elsewhere it won't find it, Make sure you have the option in the Tacviw menus checked to record DCS flights and that you have a specified a save location for the .acmi files, again it'll save to a default location somewhere odd, then check your export.lua with notepad++ and make sure the Tacview export line / dofile is the first one listed if you have more than one export running, and if you do have more that 1 try removing one at a time to see if one is conflicting with the other, then as Ajax said, test in SP first, alot of MP servers don't allow it, and ifrunning your own MP make sure to allow export in the mission options list, before you save & run the mission

either open cmd prompt on the install folder and run the installer from command prompt telling it to install the module or edit the Target line of the dcs.exe shortcut to do the same instructions here: http://forums.eagle.ru/showthread.php?t=114030&highlight=command+prompt+install

This is a bug since 1.5, it makes the AI model have a solid pit and can't be removed to fit a Human one, moving the human pit up and forwards helps with aesthetic of the overlapping pits but can create an issue that now the pit is higher, the model is a feet below you, so on landing you'll be on glide slope on the hud but the model is that bit lower down so you can end up thumping into the tarmac or flight deck

Noticed this too, found that if the nose wheel is on the ground (under aircraft weight) it is fairly hard to get the rudder to correct direction, sort of like it's glued to the ground, apply a little back pressure on the stick to pick up some of the weight off the nose once you've got a bit of speed and the rudder is a lot more responsive.

Any more work gone into these mods of late, it was starting to get interesting for the A-7E

^^ It's an Alenia Aermacchi M-346 Master although it's could be probably be easily weaponised and be passed off as a Yak-130 :D would love to see it make it into DCS as a module.

So far I've been using it as follows, Set waypoints in ME once setup and in the pit airbourne, select my WP on the INS/PCN, climb to altitude, turn to direction of waypoint, activate Autopilot / Altitude hold and use the Course set switch (+ -) to line up the arrow on the outer ring with the red divation arrow, AP will bank the aircraft and turn to set course and hold on the set direction until waypoint is reached, then adjust to next WP as needed, check out vid below ${1} I've been tryng to follow VOR but the thin white neelde doesn't seem to want to point to the correct VOR direction to what is on the maps of NTTR for example VOR 109.8 needle will fly you north east out from Nellis, unless I was doing something wrong

Try Lino's maps Caucaus http://www.digitalcombatsimulator.com/en/files/588673/ Nevada http://www.digitalcombatsimulator.com/en/files/1587399/ or http://www.digitalcombatsimulator.com/en/files/1474397/