Bog9y

What exactly are looking for with offsets functionality? I haven't fully explored every aspect of it but I can put it in offsets for TCN and waypoints. The only issue is that it's creating a true bearing instead of magnetic. This is an old function I believe, the newer jets would create the offset bearing in magnetic.

Did a quick test. Empty aircraft, full fuel load. VRST VTO page says around 4800 lbs f+w for a wet VTO. I easily did a VTO without using any water. So nearly 3000 lbs of fuel more and did it dry. Hovering at 50 ft needed around 109% RPM. Pretty sure it's not supposed to be able to do that.

LeCuvier, I once again seek your expertise and knowledge. I am trying to create 2 lines in the joystick LUA for the BINGO fuel dial for the AV8B. There is no coding whatsoever at the moment and in the clickabledata.lua this is the line: elements["PTN_380"] = default_axis_cycle(_("Bingo Fuel Set Knob"), devices.FQIS, fqi_commands.BingoSet, 380, 0, 0.01, false) I want to assign a rotary encoder to it so that when I rotate the knob clockwise the bingo fuel number increase and decreases with a anti-clockwise rotation. I have been trying for several hours now to get this coding done but have no success. I think the problem is that it's "axis-cycle" and I have no idea how to code this. Any ideas?

The charts I used are from NFM-400 published with change 5 - Feb 2003. These charts are indeed based on estimates but to climb to 40,000 in less than 1/3rd of the distance and about a 1/3rd of the time (compared to the NFM estimates) either shows that the flight models is out by a considerable amount. I'll have a play around with hovering today and see how it does with different fuel loads (maybe compare it to the hover charts in NFM -400).

Thanks guys, I'll do some more tests with the 350 KCAS and 400 KCAS charts and some higher drag indexes but I suspect there won't be much difference in the findings. I'm not trying to diss the AV8B module...I would just like it to be made more realistic. I may also see if I can find the file that controls weight/drag of the jet. Editing that may give more realistic performance. Ironically, when you do an overhead break the guidelines say , thrust idle, extend speedbrake and break at 4G up to 10 units AoA and then maintain 10 units. If I do that in DCS I very quickly slow down to a silly low speed. So for an overhead break I tend to just go idle and no speedbrake, sometimes I even leave the throttle at a low power setting to get a better abeam distance.

I'll recheck my connections...could be some dodgy wiring

LeCuvier, i have added the axis commands to the LUA file but have run into a strange problem. Every few minutes the axis that controls the HUD brightness goes from 100% to 0% in a fraction of a second, you can see the HUD flicker when it happens. The same happens with the FLOOD light but I have that one set 0% and every few minutes it goes from 0 to 100% and back to 0% , like a spike, it happens really really quickly but you can notice it. I have checked the axis curves and the potentiometer connections but nothing unusual found. Any ideas what could be causing this?

I agree with the OP. -2 degrees ND trim seems too much for STOs, I always get a nose down pitch as soon as I lift off. I rotate the nozzle exactly at the VRST computer NRAS speed with the correct NZL stop. Having the trim at 0 works much better. I think it's just the way the a/c is modeled. If you think it's twitchy during a normal VL try doing it with the SAAAHS switched off! Lots of fun doing that.

So I did some testing. Reading in the NFM-400 performance manual you get the following data for a climb with these conditions: Engine = 408 Drag Index : 17.7 GW at start of climb : 22,000 lbs (7200 lbs of fuel) CLB Speed : 300 KCAS / .75 M Max thrust climb, this is 109% / 710 degrees C JPT for the -408 engine Test carried out in ISA conditions, winds calm EXTRAPOLATED DATA FROM THE CLIMB CHARTS VS DCS : TIME TO CLIMB - DCS / FUEL REMAINING - DCS / DISTANCE - DCS SL to 10,000 ft = 0:48 mins / 0:25 / 7040 lbs / 7094 / 3.5 nm / 2.5 SL to 20,000 ft = 1:42 mins / 0:54 / 6850 lbs / 7010 / 10.5 nm / 5.1 SL to 25,000 ft = 2:30 mins / 1:13 / 6770 lbs / 6967 / 16 nm / 7.1 SL to 30,000 ft = 3:24 mins / 1:35 / 6660 lbs / 6922 / 24 nm / 9.6 SL to 35,000 ft = 5:00 mins / 1:56 / 6580 lbs / 6881 / 32.5 nm / 12.0 SL to 40,000 ft = 7:34 / 2:24 / 6430 lbs / 6836 / 53 nm / 15.3 So...yes...it's way overpowered and it gets further away from realistic performance the higher you go.

I undertand what the OP is posting and I think it is a flightmodel coding issue. The Harrier did outclimb the F-104 in real life(take off to 10,000 ft). So, down low the engine is a beast, higher up however I think it should become wheezy and not pump out as much thrust as it does. I think creating this flight model is probably much harder than your standard plane or helicopter...with this jet you have to combine the 2, I think that's how Razbam did it. I guess if you wanted to check for climb performance accuracy check NFM-400 and find a time to climb graph and figure out how long it should take to get to a certain level then compare in DCS. In fact...I'll go and do that later and let you know.

Guys, I have fixed the course selector issue! I tried to assign a 3 position momentary switch to the course selector (like we have in the DCS module) but it would constantly keep rotating the course. The coding is a bit whacky I think. Here is how I fixed it: In the JOYSTICK DEFAULT.LUA I replaced these 2 lines under the NAVIGATION panel section: {down = iCommandHSI_CourseRotaryLeft, name = _('INS COURSE SET CW'), category = _('Navigation Control')}, {down = iCommandHSI_CourseRotaryRight, name = _('INS COURSE SET CCW'), category = _('Navigation Control')}, I replaced the 2 lines above with these 2 : {down = inst_commands.Knob_Course, down = inst_commands.Knob_Course, cockpit_device_id = devices.NAV_INS, value_down = -0.5, value_up = 0, name = _('COURSE SELECTOR CCW'), category = _('Navigation Control')}, {down = inst_commands.Knob_Course, down = inst_commands.Knob_Course, cockpit_device_id = devices.NAV_INS, value_down = 0.5, value_up = 0, name = _('COURSE SELECTOR CW'), category = _('Navigation Control')}, Then in the KEYBOAD default.lua I removed the top 2 lines that say: {down = iCommandHSI_CourseRotaryLeft, name = _('INS COURSE SET CW'), category = _('Navigation Control')}, {down = iCommandHSI_CourseRotaryRight, name = _('INS COURSE SET CCW'), category = _('Navigation Control')}, and replaced it with this: {down = inst_commands.Knob_Course, cockpit_device_id = devices.NAV_INS, value_down = 0, name = _('COURSE SELECTOR CENTER'), category = _('Navigation Control')}, Then, I use RS Mapper to assign a keyboard command when I release a momentary switch (position back to center). Mine is L-SHIFT+9 and I assigned that as the command for the COURSE SELECTOR CENTER command under the DCS Control options. It may be a roundabout way to get the job done but at least this works and no more constantly rotating course selection.

Guys, I have fixed this issue! I tried to assign a 3 position momentary switch to the course selector (like we have in the DCS module) but it would constantly keep rotating the course. Here is how I fixed it: In the JOYSTICK DEFAULT.LUA I replaced these 2 lines under the NAVIGATION panel section: {down = iCommandHSI_CourseRotaryLeft, name = _('INS COURSE SET CW'), category = _('Navigation Control')}, {down = iCommandHSI_CourseRotaryRight, name = _('INS COURSE SET CCW'), category = _('Navigation Control')}, I replaced the 2 lines above with these 2 : {down = inst_commands.Knob_Course, down = inst_commands.Knob_Course, cockpit_device_id = devices.NAV_INS, value_down = -0.5, value_up = 0, name = _('COURSE SELECTOR CCW'), category = _('Navigation Control')}, {down = inst_commands.Knob_Course, down = inst_commands.Knob_Course, cockpit_device_id = devices.NAV_INS, value_down = 0.5, value_up = 0, name = _('COURSE SELECTOR CW'), category = _('Navigation Control')}, Then in the KEYBOAD default.lua I removed the top 2 lines that say: {down = iCommandHSI_CourseRotaryLeft, name = _('INS COURSE SET CW'), category = _('Navigation Control')}, {down = iCommandHSI_CourseRotaryRight, name = _('INS COURSE SET CCW'), category = _('Navigation Control')}, and replaced it with this: {down = inst_commands.Knob_Course, cockpit_device_id = devices.NAV_INS, value_down = 0, name = _('COURSE SELECTOR CENTER'), category = _('Navigation Control')}, Then, I use RS Mapper to assign a keyboard command when I release a momentary switch (position back to center). Mine is L-SHIFT+9 and I assigned that as the command for the COURSE SELECTOR CENTER command under the DCS Control options. It may be a roundabout way to get the job done but at least this works and no more constantly rotating course selection.

Probably doesn't exist but if you want I can send you the line to put in the LUA file so you can map keybinds to it?

There is a couple of Harrier FB groups....maybe it'll be easier to join them? or were you thinking of a group tailored to very specific needs?

Amazing! So you are the LUA guru! Thank you so much, I will try this tomorrow. Hopefully it's a building block to apply to other axis controls. Hardly any have been coded for the AV8B....so annoying.

id be up for that. I'm about 2/3rds done with my build

Interesting, this method worked on the IFF switch but on another, I had to use the other method of having a Valuedown of 1 / 0 and 0.5 for the middle. Have you got any knowledge of how to create a line in the LUA to be assign an AXIS? For example, I want to create a brightness adjust knob for the formation lights. It is clickable in the cockpit but there is no possibility to add an axis to control this button. I had a look at the LUA to try and copy something that has an axis but it doesn't look simple. Do you know how to do this?

Thank you so much, that works perfectly now! I guess my coding was a bit wrong. So does the "value up" mean when you put the switch to the middle position?

I've heard of DCS Bios but don't actually know what it is...looks like I got some research to do

Hi guys. ran into a bit of a weird problem. I'm trying to create a keybind for the IFF switch. It was only available in the clickable cockpit but there was no keybind. So this is the part from the clickabledata.lua: -- IFF elements["PTN_632"] = default_2_position_tumb_animated(_("IFF Operational Mode Switch"), devices.ACNIP, acnip_commands.Switch_IFF_OPMODE, 632) elements["PTN_632"].sound = {{SOUND_SW2}, {SOUND_SW2}} elements["PTN_633"] = default_3_position_tumb_animated(_("IFF Crypto Mode Switch"), devices.ACNIP, acnip_commands.Switch_IFF_CRYPTO, 633, false, true) elements["PTN_633"].sound = {{SOUND_SW2}, {SOUND_SW2}} In the joystick LUA I created this for the 3 position switch (the Crypto Mode Switch): -- IFF {down = acnip_commands.Switch_IFF_CRYPTO, cockpit_device_id = devices.ACNIP, value_down = 1.0, name = _('IFF ZERO'), category = _('IFF')}, {down = acnip_commands.Switch_IFF_CRYPTO, cockpit_device_id = devices.ACNIP, value_down = 0.5, name = _('IFF middle'), category = _('IFF')}, {down = acnip_commands.Switch_IFF_CRYPTO, cockpit_device_id = devices.ACNIP, value_down = 0, name = _('IFF HOLD'), category = _('IFF')}, I also created an addition to the keyboard LUA in order to assign the middle position of the 3 position switch. The addition is the 0.5 value command line. So, the weird problem is that in the cockpit when I move my joystick switch to the ZERO position it recognises that, when I move it to the middle or to the HOLD position it doesn't do anything. I tried swapping the down values but that didn't solve the problem. Any ideas what I did wrong?

Just amended the lua with what you guys wrote and it worked perfectly!!! Thank you so much. Is there any difference in assigning an axis command as opposed to a button press? For example assigning an axis to control a brightness knob with a rotary encoder.

Thanks, done that.

Yes but I they don't seem to be in the control options. Yep, Razbam say that keybinds is on their to-do list but quite low down. I think it's going to be a case of having to do it myself

Do any of you have the weight & balance manual of the AV-8B? In the performance manual they refer you to the NA-1-1B-40 (i think) but I can't find this document anywhere

Hi guys, I have just made the right side console and when I tried to assign all the buttons/switches in DCS I was very disappointed to see how many keybindings are missing for these panels. Basically all you have is the UHF & elec panel (minus the DC test switch). Have any of you modified the LUA file to be able to assign keybindings to these switches?