WindyTX

Took a manpad really close today something felt wrong but it took me a while to realize that the engines were in reversionary mode and a Hyd system was down, started a recovery and then got the 1st pop surge. I fly with the jet seat and VR it made me jump it felt so realistic I could not believe it and for a second there the adrenaline really spiked till I remembered it was still DCS. Thanks Heatblur and F410 for some fantastic programming. Sent from my ONEPLUS A6013 using Tapatalk

You are too heavy try 4000lbs Sent from my ONEPLUS A6013 using Tapatalk

Make sure on the stick that no A2A weapon is selected it must be off and the ACM cover must be in the down position. Sent from my ONEPLUS A6013 using Tapatalk

It's amazing that I try to give some information gleaned from experience and someone who read a book once will LOL at it. Oh and the 10 mile STT is still b......cks Sent from my ONEPLUS A6013 using Tapatalk

You mention the collision and then displacement off targets centerline. Are you gonna kill him or VID or join him? If this is TLDR the simple answer is look on TID if he is LR then put him 20 left in the DDD see if he drifts and readjust til he doesn't. 30 left collision is a 30 Aspect( co speed). What follows it what I actually do tho as a RIO KISS principle applied and it works. TBH To kill someone I just get on his nose and shoot this is Max range for the missile and as I expect him to react why mess around trying to get a fancy 20 collision. Currently in the F14 this seems to work kind of ok using the vector as a guide. When the Phoenix is launched you know how well you did by what the missile does if it turns off the rails as it lifts then you miss judged if it goes straight ahead then tick VG. When collision steering is implemented it will be easy. If I am doing a tanker join I will try and get some displacement but it's a bit TLAR. I see how much offset stops the target drifting then we are on a collision. If it starts with a 20 Asp collision then chuck him 30 off at 10nm let it drift to 40 I change this by what the collision was 40 aspect just leave it later. I then pull the target towards the nose aiming for 2.5nm at the 90 adjust the turn as required. I always have a lock for this he is a friendly so he doesn't care. If it's a VID then I still locked cos I want to see what he does[emoji16]. Miles offset from the targets extended centerline is kind of irelavant so I don't bother anymore ( tho I spent 5 years teaching it). Also bear in mind speed differential will affect but a collision is a collision. Hopefully this helps a bit till Spicemans video. Sent from my ONEPLUS A6013 using Tapatalk

If one twt is down then you can't lock and CW as you only have one. PD mode is for that situation so there should be no CW warning as the radar is incapable of transmitting CW. My understanding is that it's a degraded mode as guidance is not as robust. It's DCS tho so I have no idea what is currently replicated. Having a single twt is unlikely to be in DCS. Sent from my ONEPLUS A6013 using Tapatalk

One of my lot got into a flat spin and the RIo felt a bit off [emoji16] It probably depends how used to VR you are. Sent from my ONEPLUS A6013 using Tapatalk

PD STT As someone said you need pdStt for look down ground clutter rejection. Antenna Angle The radar tells you coverage at Max range which is a bit pants really so I now use the 1 in 60 rule and keep it simple 1 degree down is 1000ft at 10 miles, 2000ft at 20 4000ft at 40 ( approximately which is all you need). If target is 10000ft above at 40 miles then he is 2.5 degrees up. As he closes assuming he stay level then you need approx 10 degrees up. You use the elevation knob to set antenna angle and the hcu to fine tune but it only has +/- 4 degrees so be careful. "Track swap" If a tgt suddenly goes left or right very fast it is what we used to call a track swap in the Tornado F3. It means the track store has updated a second targets location into the 1st tgts store so the track jumps around very fast and is trashed you have to wait for it to see the tgt again and let it settle which can be unnerving at the closure rates. Plus in reality this may trash missile I don't know tho and ATM I believe they are active off the rails, in the second video where you see the track swap the subsequent tacview show the missiles do nothing. From what I see most people fly pretty close together as a pair in DCS so you will probably see a lot of this. I never flew in the F14 and my Radar was was way better in every regard to the F14B Until TWS Auto is working it's kind of a pain however with the current Aim54 it may not matter that much. When it is fixed it will make my 2 videos irelavant I hope. I made them for my group as we had a few questions and a lot of RIOs in training including me. Sent from my ONEPLUS A6013 using Tapatalk

Hmm what weapon are they using. This is rather a blunt statement and TBH not true I have flown against many F15 they certainly did not all lock at 10nm I rather wish they had. Sent from my ONEPLUS A6013 using Tapatalk

If I am 1v2 I will shoot both guys once I can see them separately and hope they don't track swap. I will STT right at the end if I need to. This may help it is not perfect by any means but the Tacview from each run is at the end. They are AI and the 2nd one does a stall turn [emoji16] Below are a couple of runs using STT and Sparrow. Hopefully it's useful but I don't do much in the way of editing. Sent from my ONEPLUS A6013 using Tapatalk

Well if it starts again We now know how to fix it [emoji16] Sent from my ONEPLUS A6013 using Tapatalk

Thanks for that I will try that on my mobile base . Sent from my ONEPLUS A6013 using Tapatalk

I have 2 and have seen this behaviour in both of mine the mobile one does it all the time but I find if I move it around a lot before I start it seems to settle down and then is fine for my Flying. The permanent one exhibited this behaviour once. I exercised it for a couple of minutes did a recalibration and it's been fine since. If after exercising it and doing a recalibration you can't get it to settle down I would video the problem and send it to VKB the x-axis board is pretty easy to replace as my very 1st one went out completely. Sent from my ONEPLUS A6013 using Tapatalk

FWIW. You can change your field of view using the zoom function on the keyboard to set your field if view. Personally I don't like ultrawide for DCS as unlike an FPS where horizontal view is very important you also need to be look up in the vertical. 1st rule in Air combat is put your lift vector on him and pull if you don't know any better. Hard to do if the vertical view on your monitor is limited. I use a 43 inch 16:9 for DCS when I use TIR. Sent from my ONEPLUS A6013 using Tapatalk

Thanks for that it's a lot easier to run the radar knowing what's going on. Sent from my ONEPLUS A6013 using Tapatalk

If I deliberately have a height difference and the targets descend in reaction to a shot the Radar elevation is stuck reading 0 and does not appear to change. I would assume that tws auto would keep the targets in scan and feedback what antenna elevation it was using rather than staying at 0. At the moment I have kind of given up on it and the moment I see that manaouver I switch to tws manual and keep the target in scan myself plus I can then crank if threatened whereas TWS auto is stuck centered. Between this and the fact that height coverage is at Max range and not where you have the marker ( or even half range where you try and keep the targets) the radar is pretty tricky to work with. Is the current tws auto how it worked in real life or is it this an early access iteration. The second issue I see ( again may be accurate I don't know ). I can break out that there is a pair close together in RWS but when I go to tws it only shows one target the targets will then "track swap" ( at least that's what we used to call it ) where it updates the track store when it reads the 2nd target as the primary and updates the store leading to erroneous heading ( I am making an assumption here as this is what it used to be in my previous life). Solved by waiting for it to settle then re inserting but a bugger if it happens as you shoot. So again is this an early access situation or a realistic representation of the radar or early access simulation. Thanks for the module great fun and you have the multicrew working way better than I expected. Sent from my ONEPLUS A6013 using Tapatalk

This is you vkb gunfighter pro on a Virpil deskmount and a Warthog base plate but it took some drilling for the holes and some milling to get the sticks connector through the baseplate hole. Yep you sit away from the desk great for DCS but not so good for anything else. Sent from my ONEPLUS A6013 using Tapatalk

Hmm the one that reads 98kts right now appears to move and I haven't managed to set it. I'll admit only tried a couple of times but it appears to move on it's own. What does it indicate ? Sent from my ONEPLUS A6013 using Tapatalk

Yea it's not in the regular one it will be in the restricted one. Sent from my ONEPLUS A6013 using Tapatalk

I think this problem is 90% down to the lack of g feel available in the sim. I have broken the wings twice since release once trying to avoid the water, in both cases I snapped the stick back which is a bad habit gained from the F18 flying and relying on it's FCS. In the old days we used to pull to 5 squeeze to 7 (when 7 was available [emoji848]). In a real aircraft it's pretty easy to pull to 5 as it's when the g suit is fully inflated (as long as you didn't snap 5 [emoji16] ). In the DCS F14 I now allow more altitude in my SAM defense manouvers and try to always squeeze the stick to the desired turn rate and try to be as smooth as possible. While in a fighter you don't have to worry about the g&t's in the back it's generally good practice to fly smooth and your RIO will probably appreciate it, they certainly do in real life. The g meter in the F14 is in a ridiculous location and this is way more of an issue when you can't feel how much g you are pulling because you are in a Sim not a real plane. Sent from my ONEPLUS A6013 using Tapatalk

It worked for me multiplayer the other day. Just remember to push the fire switch back in so you can restart the engine if you had to shut one down !! Sent from my ONEPLUS A6013 using Tapatalk

LOL I am known in my group for always wanting a hot Aircraft. I am 55 and life is too short. Spent 10 years waiting for my back seater to align the INs, I cant afford to waste any time at my age. Too each his own tho thank goodness ED gave us the option. Sent from my ONEPLUS A6013 using Tapatalk

Not much help but SOP is for the pilot to always take the shot anyway. That being said it has worked in the back for me but that was just a test we do not operate that way. Sent from my ONEPLUS A6013 using Tapatalk

+1 Had similar damage today skidded in a 180 but didn't roll over managed to repair unfortunately I forgot to reset the fire handle so couldn't start the right engine doh. Respawned in the end for another long transit. Nice job Heatblur was well p'ed off during the transit chatting to my back seater when I realized what I had done wrong. Would really like and approach end and overrun cable if ED could manage it. Sent from my ONEPLUS A6013 using Tapatalk

Having messed around for a bit in the F14 I understand your attitude now Victory,. Seems like the USAF procurement team were a little more successful [emoji6][emoji6] Sent from my ONEPLUS A6013 using Tapatalk Sent from my ONEPLUS A6013 using Tapatalk