Mirage2425

Thank-you for the detailed explanation. I understand, but am disappointed. I wanted to use steerpoints to mark SAM launches for SEAD/DEAD with Mav's or cluster bombs instead of HARMS. I don't think the DTC is something that will be ready for a long time. ED's focus is elsewhere. So it may be a very long time before we see this feature. I'm hope I'm pleasantly surprised but I think that's not very likely. I also agree with you on the steerpoint system. TGT's are another example and I'm not sure if offsets can be created. The means no VRP/VIP functions for a while either.

I'll try it again and report back.

Now that we have clouds in DCS I've gone back to practicing my instrument flying. I've noticed an issue with the runway lights. They aren't on during the day, even in inclement weather. As a result, I don't see the runway until I'm on top of it. In my testing so far it seems the lights turn on after 7p. Communicating with ATC doesn't seem to turn them on either. Is there any way we can turn the runway lights on all the time in inclement weather? Or, tie them to ATC?

Would it be possible to place Mark Points high on your list of priorities for the Viper? Just basic Mark points, integration with the datalink can come later. It would be a quick win, you already have much of what you would need already in place. Mark points from the HUD use VIS mode so you could pull that right from the Maverick. You should also have the coordinates from where the sensors are pointing, in particular the TGP as we don't have A2G radar yet. Steerpoints can be created manually so it probably wouldn't take much to save the steerpoints in one of the slots dedicated for Mark points (26-34, I think). I'm just an end user and I don't understand the complexities of what you are working with. However, as I said above, it may be a quick win for you. I'm sure many Viper pilots would really appreciate it. Many of us want core features to be completed before more weapons. Thank-you for considering my suggestion.

I'm trying to keep the FPM on the horizon. I was holding the same stick position. If I let off the stick wouldn't that increase rate? I need to try it again. It's been a while and I've been focusing on A2G. That is my recollection though.

I'm definitely not doing that. I'm only pulling to the green donut. The stick isn't full back. Trying to just maintain 13 degrees of AOA.

What exactly is the limiter? I've never found a good explanation. I'm only pulling to the green donut. The stick isn't full back. Trying to just maintain 13 degrees of AOA.

I read somewhere if you pull to the green donut on AOA the Viper will sustain rate. This may be an incorrect perception.

Hey Mover, I love your books, I've read most of them. I have a question about the turn performance of the Viper. If you can't answer I totally understand. What is classified should stay that way. Can the Viper sustain a turn when you pull to the green donut (approx 13 degrees of AOA)? I've noticed that ED's Viper tends to maintain that AOA in a turn for a few seconds and then AOA starts to increase dramatically and the jet bleeds airspeed. If you can answer, is this accurate? This kills the Viper's turn performance, making it underperform vs other aircraft in DCS.

So no HUD symbology yet, but there.

I guess this post was premature. It appears that both of these DED pages are in the jet already. Not sure if they work, I'll try that in a bit. What it does confirm though is that these capabilities will be in the jet.

Is the VRP and VIP DED pages along with the associated HUD symbology a planned feature? I can't find any information on them.

Better yet, use TWS. Then I dont have to wait for the missile on the lead guy to go pitbull before going after the second guy. Just so long as the other guy stays within the gimble I should be fine. I'll try it tonight.

Got it. I can wait for my missile on the hot guy to go pitbull and keep an eye on the aspect on the wingman. Then, lock the other guy, pull him into the HUD, launch, crank, wait for the missile to go pitbull and defend the missile that is likely to be coming at me from the hot guy.

Got it, offset. Just learning the BVR stuff. It will also slow closure.

So, if I crank will that resolve the issue? Then we are at 45 degrees aspect instead of 90 degrees.

RCS meaning radar cross section? I've tried to use expand with no luck. The wingman was flanking while lead was nose on. Maybe he was notching my radar? I'll try to acquire in RWS first and see if that helps.

It was set to 30 degrees and 1 bar.

Has anyone else noticed an issue with the TWS radar where contacts only appear on the radar about 60 miles out. Then, the contacts wingman doesn't show up on the radar at all. You see the contact on the datalink but not the radar. The wingman is at coaltitude with the lead bandit. Shouldn't I be able to bug a target from further out than 60 miles? Also, shouldn't I be able to bug his wingman that is very close to his lead and coaltitude?

It was my fault. It had been a while since I had boresighted the Mav and I put the handoff mode in auto. In retrospect it was stupid, since the mav isn't looking where the TGP is the mav will never lock. I needed to be in manual mode, switch SOI to the WPN page, move the crosshairs over the same target on the TGP, TMS up and boresight. I should have watched Wags video again before I posted. Thanks for the help!

Thanks Badlego, I'll give it a try. Whem I was boresighting the Mav didn't seem to lock when all parameters for a firing solution were met. I must be doing something wrong. I'll work on it until I figure it out

I've been air starting the Viper lately in the interest of time and have been practicing with Mavericks. Today I decided to ramp start instead and when I went to boresight the Mavericks the option was missing on the WPN page. I hit the OSB where it should have been anyway but was unable to hand off anything (cross expanded as if out of range or too far off boresight). I'm assuming it was due to the inability to boresight the Mav's. Perhaps a bug been introduced in recent patches?

You are correct, I was compensating for too much roll trim. It's just a little now. The ball is still touching the left line. Not sure if that's supposed to be that way. However, given the small amount of deflection I could see the ball being centered before I start trimming.

How do you set the mouse wheel to clicks?

That's usually what I do. Let me see if I can get some screenshots amd a track file. I'm using VR super zoom. I'll post them once I have them. It's good to know that you don't experience this issue and it's probably something I'm doing wrong. That I can correct It's not that I'm out of yaw trim. It's just that it's not working as I'd expect, meaning center the ball with yaw trim and then correct with roll. I'm only moving the knob about 1/8 of the way to the right, which moves the ball left. Then I can use roll trim to correct and perfectly trim the aircraft.