Invisibull

Unfortunately, this made no difference for me. Thanks anyway.

Hi folks, I updated my openbeta server today but then when i went to run it the first time, i inadvertently closed it before it had fully loaded. Now it gets caught in the loading screen and hangs there indefinitely. I have uninstalled/deleted everything and tried to start over from scratch, but it's still happening. The log it generates is not very long so I'll just paste it here: Any help would be greatly appreciated. Thx.

Frankly, when I compare the above hearsay (we certainly have no way of knowing exactly what "T-DAY" said and what the context might have been) to the account from the Semper Viper! article, it's not even close which of the two should be more heavily weighted as a useful source to answer our inertial roll question. Here's the relevant excerpt from that article: Currently, nothing I can do with my FSSB stick will "stop the roll rate completely" as described in the above article. Also, when I do try to stop the roll now, the response is anything but "rapid." No disrespect is intended here, but I spent the last couple of years really enjoying how well I could stop the viper's roll on a dime and now I'm being told that that behavior was incorrect all along even though we have direct quotes from the horse's mouth verifying that it was perfectly fine in the roll regime (at least from a FSSB user's perspective) before the FM update a month or so ago.

Did that internal build not make it into today's update? It def feels different to me. Maybe a placebo effect. I'm sure others will comment shortly. UPDATE: Upon further testing, I guess it hasn't changed as much as I first thought.

Today's update seems to have improved this issue.

This is exactly how it was with my FSSB until a couple of updates ago. I know it might sound a bit daft, but I really miss that aspect of flying.

If Wags is saying that, then I have faith that it's already fixed. thx.

Same here. I don't understand how ED can say "Correct as is" in 2019 with no roll inertia, but now say the same thing with lots of roll inertia? It defies logic.

Interestingly, a couple of years ago someone complained about how quickly the roll stopped and the post was marked [CORRECT AS IS] So, the fact that that's obviously been changed recently means it must be incorrect as is, right?

Bricks still unbuggable for the first 20 seconds after today's update.

If I'm remembering correctly, the initial bricks didn't show up until they could be locked. What's seems to have changed, and what has confused me, is that they now appear a good 20 seconds (when we're flying right at one another, co-altitude) before I'm able to bug them and begin setting up for a shot. That's the real issue in a nutshell.

Thx for your response. I'm a bit confused about this comment as I was consulting the DCS Viper Early Access Manual along with Chuck's Viper guide while writing my original post. I'm not saying you're wrong, but that I'd appreciate knowing what terminology I used, which applies to the Hornet, but not the Viper.

Thx. I did see mention of an impending "white paper." I hope it turns out that this will be changed because it's not a very intuitive way of managing radar contacts imo.

Hi all, Just wondering what's going on with the bricks when using RWS in a BVR engagement. At a certain point (somewhere around 45 nm for a co-altitude MiG29 heading directly at me for instance), I get a search target brick like in the attached pic. null My understanding is that at a certain point, as the track file is built, that there should be a visual cue represented by a chance in color/size of the brick in order to bring it to the pilot's attention that the search target is now a track target and they should be able to bug it at that point. What I'm seeing instead is a brick that never changes color or size that I'm suddenly able to lock, but only after TMS up'ing multiple times and allowing it to get within roughly 37 nm (again in the instance that same MiG). Is this now considered "correct as is," or will it be changing sometime soon? Thx.

Except the toe brake travel. Knees.

My apologies, I meant 90 degrees.

Unfortunately, I'm already using the combat pedals. What angle is your knee when using the toe brakes? Mine's around 45 degrees and I feel like to apply full brakes, my calves are having to flex way too much, making it very uncomfortable to hold the brakes down for any length of time. I'd estimate the travel is about double of my saitek combat pedals, which I've had for like 12 yrs. I only got the Crosswinds because I was getting a little knee pain from Apache'ing so much.

Thx again. I've also done that, but I'd much prefer "feeling" when I've got full brakes applied like with my last set of pedals.

Thx, I've done that, but my issue is with how long the travel is to apply full brakes.

Thanks for all the comments. I ended up getting the Crosswinds and as rudder pedals they are exactly what I was looking for. My problem now is that I find the travel of the toe brakes is about twice longer than I'm used to and pretty uncomfortable when taxiing. Is this at all adjustable?

Are you saying that you can basically adjust the force required to get full deflection to almost zero? I don't see the ability to remove the spring mentioned in this video. thx.

Hey Guys, Just looking for some input as to what are the best pedals to use with the Apache considering I'm using Saitek Combat pedals now and they are a little rough on these middle-aged knees. Anything really solidly built with very little force required? I looked into a Virpil set that was recommended to me (spring can be removed) but 53 cm is a bit wider than I'd like (but if they're good enough, I can prob get it to work). Thx.

In a PvE environment I've noticed that using the jammer all but guarantees your radar won't support any locks for very long, often dropping lock before your slammer can go active. I really don't see the point of using it in a BVR engagement as its currently modeled. Of course I might be missing something and if that's the case, I'd love to know how the jammer can be of use.

Thx, i think you’re right. I will try that next time it occurs.

The white hollow box at 14K appeared during a MP engagement, but just stayed in the exact same position even 15 min later after I had landed. I don't remember seeing this sort of things before. Any ideas?