WildBillKelsoe

No I can input coordinates and the TGP unlocks to them correctly in CCRP. However, the steerpoints coordinates are changed as the TGP tracks objects on the ground. It should be steady on the coordinate as if you're referencing bullseye. My gripe is the PROJECTED BOMB IMPACT LINE. The STEERING LINE for CCRP is not looking with the TGP. The CCRP system is off.

meh...

I'd like a C-130 for the cargo operations/paratroop deployment. With all the trimmings. Pomme frites... That is like captain sims C-130 with the load master sheet, the effects of cargo on CG/handling, and animated paratroops/ cargo drops with parachutes and cargo hold camera <3 <3 <3

I will try and fly the mission (air start) but for now I have made a youtube video of the problem

This means that a target locked in point track mode say 10 degrees OFF the nose left, the PBIL and thus the in range countdown tick mark are aligned to the right of the nose when both should be tracking one piece and providing steering cues. Maybe its the A-10C shadowing how I understand the mechanism but here is what I do: 1- on the ground cold, STP00 = LAT/LONG from Lcrtl+Y when on NAV (INS assumed aligned after 10 minutes on either ALN knobs). 2- Call JTAC, get LAT/LONG. Write down dividing seconds given by 60 to get the proper format. 3- On NAV master mode, hit STPT, cycle to STP01, punch in Lat/Long after step #2. Along with AGL from TACs 9line. 4- Once done, enter AG mode with TGP on and mode CCRP. Laser switch up. 5- CCRP mode directs crosshair to intended target and locks it in point track mode. 6- on HUD, no visible TGP cue indicators so use the dot on the TGP page to get the nose pointed directly at target. 7- PBIL and its countdown does not want to move with the target relative to nose position. Pointing elsewhere. Only relying on distance from many bombing steps before to release in pseudo-CCRP with a misaligned PBIL, then fire laser and lase in hopes the bomb would correct and home in on target. Is this a normal behaviour or should it behave differently?

True, but I wanted this to work considering Wags' heavy emphasis on the systems during startup videos.

I've been hit three times by 30mm AP rounds from a Su-25 but don't know where but the ' key does not show any failures to the systems and my radio just dies without being reported hit or any master warning or cautionary lights.. track save 1 https://drive.google.com/file/d/1lcv2qF32UNilGcJzpdtdZPNkn3jyOfLf/view?usp=sharing track save 2 https://drive.google.com/file/d/10xrlQ5n0qox9M7hLxlKDasvID_caJ1BY/view?usp=sharing TACVIEW https://drive.google.com/file/d/1JuSGhUU_UkxpCoMefuCTo6pboCwjEt8e/view?usp=sharing

Thank you for getting back on this. However, I believe that something like this should be mentioned in the briefing for the mission. But thanks anyways.

No you need to go to altitude 200 meters AGL referencing your altimeter (not radar altimeter). If he says "ALTITUDE TWO HUNDRED!" you're approaching limits and must correct altitude right now. Do not touch the altimeter at mission start except if its not calibrated to QFE (reading zero).

I spool up and takeoff following W1 obeying ATC for MSA until off their radar but now three times I try to follow W1 and always as soon as the last thing about water reflection is said, both N1/2 needles leave each other and I crash. I've took a video as it happened and I also got a master caution although the instruments showed all in the green. The track is too big (58mb) to attach here (5mb file limit) but this is the screen as it just happens before the powerplant fails. Not a single caution on the warning panel...

This might look bad to hardcore people here but I would like to be able to input characters and numbers directly on the prompt cursor when depressed and flashing without having to cycle through each character in the string using the knobs. Just a syntactic sugar or a thought to devs. Makes life alot easier when punching coordinates on a regular basis. Albeit if not that realistic. Hence if its OPTIONAL would be great.. food for thought.:thumbup:

+1

clear category to ALL and AXIS COMMANDS to the F-5E module. Exit Restart system Boot DCS Remap ALL and AXIS COMMANDS controls to F-5E module again. Report if this solved your "rolling" tendency from the looks of it, sounds like you have duplicate controls.

and dont forget... THE LSO CAMERA!!! +10000000000

so is this coming or abandoned? I have a bricked TMWH and I like your design. I don't think I want to invest time with TM..

Its the first time it acts this way.. I plug it, the lights come on momentarily then off... then I get the windows 7 can not recognize device. The stick is OK. I tried the boot loader method described by TMWH but it doesn't even read the throttle. I tried a different computer, same outcome. What causes this?

where were you 5 years ago?? Wunderbar!! Danke. May I suggest you also do the same with German warbirds?

that's 0.03 not 0.3 :D

That is really odd considering that liftoff occurs past 70 knots thus NWS must be off to handoff authority to the rudders and prevent nose over from aggressive nose wheel turning.

Didnt nws autodisengage above 70 knots?

You mean to tell me real hornet pilots struggled with this? The inability to assign pages to master modes?

IMHO they should set the FLIR first given it is shared among many other aircrafts and helicopters.

wasn't the TGP supposed to be implemented following the FLIR engine upgrade?

yes because your radar beam is not just stopping at the tanker it continues way past it. So anything that flies perpendicular to the radar beam, gets in the notch. That is why in many of youtube videos ( ) , also when you're being engaged with a , you defeat it kinetically by being offset to it 90 degrees so its onboard radar emitter or the launching platform does not track you because you entered the notch.

you need fromage to go along wiz your mirage...