_Hoss

Did you go TM for new set-up? Or really go all out with Brunner?

McDonald Douglas became Boeing Jan 98. Do you know when this video was made? nice video though...

Virpil, VKB, or WW?

Would love a Korean map over the Faulklands. You can use the Korean map for modern what if scenarios too. But we need the straight deck Essex, F9F, F4U-4, and of course the awesome A-1. AI B-29's.

I don't know much about Simap pro so I'm just guessing here. I use TARGET and Sedenions Complete 128dx Script. So all of my keypresses are dx commands, which work for all the kneeboard functions. I had thought SimAppPro was for using GUI script i.e. using your controller as a virtual keyboard (CTL+SHF+X) type commands. Hope you get it sorted nikoel. Cheers

I imagine these adjustments are in a Lua file somewhere?. If that's the case where can it be found. All I see for adjustments are the axis tune gui in game. Thanks for the info

I took all the screws out one by one put a small bit of lock tight (very small) and tightened them down. I also have a collar that goes around the shift of the stick just above the collar nut and below the grip, that stops torque/stress if I push the stick to hard against the stops/limits of the shift. I'm also using a 10mm extension. It's very secure now, no slop anymore.

Link the thread please, I've got a four month old GGD sleeping on my chest. LOL! I hope the bomb arming is fixed too. The Mossie had the exact same bugs, incorrect analog trim, and none of the keyboard presses I assigned would work from my controller, but worked when I pressed the keyboard. Same keystrokes worked on the Mustang and Spit from my controller (Blackhog). I wish they would expand their testing before they release updates, with dedicated module testers to see if the Hornet, Falcon, Viggen updates bug other modules. Especially the warbirds.........

It works great for the A-10C, I had forgot the EAC, and RDR ALT, switches have to be enabled for it to work correctly. But the DX script is good if you enable the one Sedenion mentioned in the post above.

I don't have TRP Pedals, but my set up window shows all the TM devices that are programmable, only the stick and throttle have their little GUI button lit saying they are connected. They also show which firmware is loaded, so if you don't see all the devices and the ones connected, TARGET is not installed correctly. I'm on my pad so I can't take a screen shot of what you should be seeing. But I would start there, youtube search on how to correctly install drivers and update firmware, it's very easy. I do not plug in my TMWH into a POWERED USB hub, but directly into my MoBo, Crosswinds too.

Is it module specific? i.e. warbird, jet? Do you have TARGET installed? Is your Firmware up to date for the pedals? Each controller has a firmware. TARGET will allow you to look at and set up your rudder and brake axis. There are numerous modules with analog axis bugs...... with the Jug being the worst. Hope you get it sorted. Hoss

The Jug is even worse, can't use analog axis trim R/P/Y control box, and weapon controls are unusable with controller assigned keystrokes(1 - 9) DX inputs work, butt not the assigned keystrokes. Mustang works great with the controller assigned keystrokes. This is the main reason why I usually give up on DCS ever working right and go back to the other sim. Feels like a huge waste of money and time, and the developers and DCS could care less it seems. What really erks me is it used to work, the Mossie was just as bad with the analog trim, and arming commands, now they work again...... but for how long?

If its not broke, don't fix it. But if you do, don't skip steps. Read the procedure a few times before to attempt it.

TARGET GUI is very easy to use, SCRIPT is another animal entirely. GUI gives you an IN/OUT function on the stick, usually S3, it gives you UP/MIDDLE/DOWN layers on the throttle. I don't use the GUI in DCS, I use the SCRIPT developed by Sedenion, and turn it on with the script function. I get 89 DX buttons to assign to a DCS function, with TEMPO short/Long presses. Invest some time learning how to use it and you will be happy you did.

F-84 in any form would be great, along with a Koren map. But an Essex carrier with a F9F, A-1D, F4F-5.... heaven.

The analog trim function is still broken in the Jug, and it was not mentioned in the release notes for this latest Open Beta version. The Mosquito has been fixed, the analog trim works, and my BlackHog controls the bomb arming functions using keyboard commands vice dx commands. The P-47 bomb arming functions work on my keyboard 1 - 9 and RCTL 1 - 9, as I assigned that to the keyboard column in controls myself. My Blackhog will control it using dx commands but using control/keyboard commands via the blackhog is bugged. It worked fine before and I'd like to have the functionality back. I assign a list of commands (Sequence) to the blackhog using joy2key, it works in the Mustang, and Mossie now after this last update. So now I'm back to using my TMWH trim hat for trim, and using the mouse for bomb arming functions. I don't have the stable version loaded so I can't speak about whether its broken there or not. Signed........ Frustrated Jug Jocky.................................. Cheers

Before you replace it remove it and use a ohm meter and check the P-N junctions. If they check good solder it back in and see if it works. Sometimes the solder joints degrade with vibration, heat, cold. Find a good sight that will give you the characteristics of your part, most of the time you can find a suitable substitution. Or just get a new board from TM, when all else fails.

The common Avionics differences between the C/D and E/F are slight. The SDC (Signal Data Converter) which supplies the information displayed on the IFEI, are physically the same size, same number of SRA's inside. Its just newer, with newer components. Which is very critical, because a lot of the IC's and discrete components are rapidly becoming obsolete and un-obtainable. This goes for all the other Avionics systems in the C/D as well. The only thing that needs to be modeled between the C/D and E/F are the avionics systems not in the legacy birds. Lot numbers are not really that important either. A "lot 10" bird when it goes through SLEP will get updated to the current lot capabilities, hardware, software updates or OFP's . SDC's went from -8 models to -10's old -8's were modified to -11's. The -10, -11's are electronically the same... inputs/outputs..... physically the same size but the SRA's if you know what you are looking at you see the differences, especially the MOD wires. And both SDC work exactly the same in the plane. There are three dash numbers to the UFC, looking at it from the cockpit you would never know the difference, some are modified Non-Night Attack versions. Most of the control boxes, displays you see in the C/D I have repaired/modified, and the WRA's (Weapons Replaceable Assemblies) they control. The Marines are the only ones still flying the C/D in the US. Spain, Finland, and Malaysia would send gear they couldn't fix to us for repair. It will be around for awhile until said services retire and replace them. You have to remember the Navy only has so much space on the ship, Avionics work centers have fixed floor space for repair benches, fixed number of personel. Supply can only store a certain amount of RFI (Ready For Installation) or "A" condition spare WRA's, SRA's, and repair parts, for all the aircraft on board. That also goes for Structures, power plants, GSE, Ordnance. Navy techs, no matter the discipline are trained on a very wide range of systems within their rate, NEC families. Cheers The Ogre Hoss

Are you using TARGET GUI, or TARGET SCRIPT for programming all your modules? I imagine the DX SCRIPT if you use this assignment diagram. I use GUI for IL2, and Complete DX SCRIPT for DCS. For IL2 I only have one profile using IN/OUT, UPPER/MIDDLE/DOWN layers so I can get enough buttons to only use that one profile for all the A/C. So I use the print function and save that to my dump truck SSD. The DCS SCRIPT version I can't do that with, so when I get on my computer I'll give your program a look. Thanks.... You should post this on the HOTAS/HOSAS/SIMPIT Discord page. Thanks again Hoss

Get your facts straight, I did not ask for it. I held a SECRET clearance for 44 years, I repaired DECM, and COMSEC equipment in the Navy. At the ARF I worked APG-65/73 RADARS. Being lectured on guarding classified information is a non starter. I'm amazed at threads on both systems I read in these forums, I know how it works and DCS doesn't come close to getting it right because they can't. DCS module developers are working from released public documents, and common theory of operation of like systems. And input from SME's. Oh, I was never a "Seamen", and its Seaman, aviation rates are Airman......our rates have wings..... The C/D and E/F Blk II is just as classified as the BLK III. Your argument is moot. Cheers Hoss

That's a shame, extremely bugged modules is the reason I usually leave DCS to go back to the other sim. I've always thought having an open beta was for a wider range of testers to look at all the modules, and fix them quicker. Guess that's what I get for thinking. Back to the Mustang!

Hey Sabot, how ya been brother? I'm still training on the Hornet so I can come fly with the group. I see Taz is back too....... give the gang my regards Hoss

After further experimentation last night with the Jug, I found out it's much worse than I thought. All the L/R/B bomb arming/jettison controls on my BlackHog don't work, everything else does, I had to go through and assign key presses for bomb/rocket arming/de-arming and jettison in the P-51, P-47, Mosquito (1 - 9, RCTL + 1 - 9) I came up with a database so I would not be stepping on other keystrokes in a module. I combined those keystrokes and tried to keep them as consistent as possible between modules. Well they worked great before the update, now they are borked in the Jug and Mossie, the Mustang still works like I programed it (joy2key). So that tells me my BlackHog is working as advertised. Beta testing modules is very bad in DCS before a release is put out, they look for discrepencies on fixes module upgrades developers are doing and skip the others. We all know that is a common occurrence after every update. The release version is just as bad. Most of the servers I fly on when I get the chance are Open-Beta servers, and the individuals I fly with all use Open-Beta. So it's disconcerting when the modules you love to fly are gathering dust and getting worse with every update. I guess we will have to get up a Truck Convoy and head to DCS/ED and blast our air-horns...................... I'm probably going to get more naughty boy points from the admins......... Hoss

No, F/A-18E-F's going into overhaul are being updated to Advanced Super Hornets, or Block II to Block III, not all but a good majority. And some are being built from scratch. I'm retired Navy, and retired Boeing, so I've known about this for awhile, Did you know some of the Super Hornets sent to Australia are wired to become Growlers if the RAAF should decide to convert them? Oh yeah, the first Block III has been delivered to the US Navy already.................. Nope, no Troll, Ogre maybe, but no Troll. So if you are going to ask for something, ask for the latest iteration of the Hornet. From the Boeing web page on the Block III Hornet..... https://www.boeing.com/defense/fa-18-super-hornet/ Cheers Hoss the Ogre

VA-165 was on the Connie when I was ships company 2/79 - 6/82, we had VA-146 Blue Diamonds, and VA-147 Argonauts. VFA147 is the first Lemoore squadrons to convert to F-35's and is the squadron that lost the F-35 on the Vinson. Ooops... We had VA-95 on the Lincoln for the A-6 squadron in CAW-11... and of course my two favorite NASL squadrons... VFA-22 (YCBAR), VFA-94 (SHWFOTS). Hoss