ACME_WIdgets

This is a SWAG long shot, but based on my very experience in drone building: KALMAN filters are mentioned in the latest update, I think for the AIM-120C. Kalman filters are considered to be 'efficient', but I know they can take up a lot of RAM space. Where any Kalman filters added with the general 2.7.7 update?

I probably have THE slowest machine. 2.5.5 was about 20fps, then 2.5.6 12fps and a clean install of 2.7.7 is now at 9fps. All SP same simple FC3 mission start at 4000 ft. ALL settings as low as possible/off. 1280x768 res (but on a fast 144hz monitor - don't ask). Technically it shouldn't even run on this laptop.

For the F15/FC3 HUD color, I scroll past the red options to the yellow/white color. Works best for me.

Did you see a fps drop with the latest 2.7.7 version? please reply or comment with: - Yes or No - Beta or Stable - fps drop OLD fps to NEW fps - any other details you'd like to include No discussions please, let's just try to generate numbers for ED. Thx

Dear DCS, I'm in the global electronics manufacturing business. Our company buys over $1B in components a year, and we expect the current IC supply crunch to last at LEAST through the end of 2022. Therefore, I don't expect any RTX30xx GPUs to be in great supply any time soon. IF the DCS engine performs poorly with existing hardware, and DCS places further demands on PC hardware - with most people NOT being able to upgrade - then I suspect DCS will start losing more and more players (with almost no new players signing on). Just my opinion. I hope it's not the case, as I love the simulator. p.s. - I've been trying to find a RTX 3070 or 3060 ti for under $800 (with a warranty) since February, with no luck.

@BIGNEWY Since we're talking about BETA, can you roll back only the water enhancement to the 2.7.6 level? I'm sure feedback would be instant if fps increased. If no fps change, then you know it's not the water enhancement.

@Flappie I'm just pointing out that Comcast does filter/monitor downloads. I'm no IT guy, but maybe this effects download speeds??? Are big DCS files filtered like big movie files - I don't know.. Sorry if this adds any confusion. When using my Comcast ISP, I get about 8mbs avg download speed from DCS. If I check on Fast.com I have a possible 56mbs download speed.

IF the water details is the problem for the slower fps (and I have nothing to base this on, other than the water improvement announcement in the new revision notes), does anyone else (with a slow system) notice at mission start water is covering EVERYING, and then ground gets placed "on top" of the water? Is DCS rendering water underneath the ground? Might explain the fps hits over the middle of the desert... (this is pure speculation, so take it with 2 grains of salt and don't call me in the morning)

IF this slowdown is due to the enhance water effect, why doesn't DCS have this as a toggle in Options?

I have Comcast ISP and Comcast filters/monitors download traffic. For instance, If you download a copyrighted movie, they sometimes email you a warning you that you downloaded copyrighted material. @Flappie

I'm on an old Dell laptop with NVIDIA GPU 5200H, with F10 crashes.

Same for me. Switch to F10 and then zoom in or out right away and often crashes in MP (GS server). If I turn OFF labels, target areas, detection areas, etc. it seems less likely to crash. UPDATE: The "crash" is not typical for me. The DCS screen disappears so I can see my desktop, but I can still hear sound and I DCS is still running under Task Manager. When I try to click on my desktop nothing happens. I have to Stop DCS in Task Manager to shut it down. Submitted crash report a couple days ago.

F-16 stall speed is: with 1000 lbs fuel, gear down, no bags, having fired 6 120Cs, 200 Above Sea Level, no wind = about 130 knots. (Just start in ME at 175 knots, drop the gear/bags, fire the missles - and see how slow you can go and still maintain a CONSTANT altitude. Why "about" 130 knots, is because the digital flight controls don't want the plane to stall, so it gets really nose high and mushy below 135 knots. At about 130 knots you cannot pull the stick far enough aft to maintain altitude.

@MoverMy comment about ideally landing 1 knot above stall speed is idealistic. In real life plane landing, the closer you are to the stall speed the less likely you are to bounce - plus you can apply more braking force faster (slower landing roll out speed = less lift from wings during roll out = greater braking effect)- all resulting in a shorter roll out after landing (i.e safer roll out). When learning to fly real planes, when landing (in ground effect) you are often told to keep pulling the stick/yoke back and back as you are in ground effect just before touching down (kind of like slowing and stalling just before touchdown). In the F-16 or other fighters you fly the plane to the ground (i.e. keep some power applied (to avoid excess sink rate = they don't glide very well).

And if the approach is steep or really steep for some reason, start the flare at 150 - 100 feet AGL. If you also have high speed, the flare slower so as not to porpoise. In general, ideal landings are 1 kt above stall speed, so no chance of bounce and shortest rollout.

Zoom level on my system (incredibly slow, underpoewered) has a HUGE impact on FPS in 2.7 when smoke is displayed. When I am zoomed in to look at MFD for F16 Maverick targeting and fire a Maverick my fps drops under 5 fps. If I'm zoomed out, or "normal" zoom/view and fire a Maverick I see only a small fps drop.

I don't know, does the flight model stop running after a certain amount of damage? (just a guess) But, from my testing, I thought the scenery was the cause of the big fps drop (i.e. P-51 fps = F16 fps = F15 fps (with same scenery settings) - but all have different flight models).

Closely related, is there any way to get BACK to the INS alignment screen on DED (while INS is aligning) if I use the DED for something else? I like to enter steerpoint, change othe ICP/DED etc. while INS is aligning. But then I don't know if INS alignment is complete...

My PIA way to do this is for MP is, on the parked ground before takeoff: 1- Look at HSD for SAM center. 2- Estimate range and direction from my A/C. 3- Open F10 map and measure approx distance and direction from my A/C parked. 4- Write down Lat Lon of estimated SAM site. 5- Enter new Steerpoint with Lat Lon of estimated SAM site. 6- Look at HSD to see how close you are (is Steepoint cross over SAM center?) then correct Lan Lon as needed. 7- Go back to F10 and get Altitude of SAM estimated location. 8- I now have a Steerpoint with 3-5 ish nm of SAM site, usually good enought for HARM. 9- Copy SAM sites to Kneeboard per MP Server for future reference.

"Just FYI - Since you mention using the rudder - I presume you are trying to decrab the viper on landing. Standard operating procedure is to NOT decrab the aircraft to align with the runway. You land crabbed. Feels weird, but actually works pretty well. " Hi @Deano87 - I am referring only to ON the runway use of rudder with a cross wind. Crabbing for landing is no problem for me.

Right now, when a crosswind is present on takeoff or landing, the amount of rudder input to maintain a path on the runway centerline is a constant amount of rudder input - even as speed increases. I think the rudder input for the crosswind should be LOWER as speed INCREASES. i.e. 60kts runway speed in 20kts crosswind = large rudder input to stay straight I think 160kts speed in 20kts crosswind = smaller rudder input than at 30kts speed. This is really a problem for me when I turn OFF NWS around 100+ kts. I have to input even more rudder to correct (yes I get that NWS helps maintain a straight track). And some MP servers use 30hts crosswind. Also, while flying the F16 at low speed, in my opinion the rudder input injects way too much roll. Yes, the rudder is not 90 degrees perpendicular, so some roll coupling will occur. But it just seems too high, based on my propeller real pilot experience (including some aerobatic SEL planes).

Attached is my TRK file. I enter AG, wait for the BB radar, then move Left MFD WPN cursor with analog mini-stick/hat. Cursor is way too fast, then I switch hat to "button" emulator and it works OK. Same mini-analog hat works great in BVR FCR mode. Thanks for your help ! @Flappie F16 HARM left MFD analog cursor then buttons.trk

I use an older e6850 at 2.9Ghz only 2 cores. FYI, remove the bottom cover, and prop the laptop up about 1 inch and it will run 15-20C cooler. Don't touch/block the fan or cooling pipes, etc.

As far as things not being clickable: I've noticed certain resolutions introduce a mouse location error in the vertical axis. What I mean is the display is fine, but I have to click above or below the switch to get the mouse to work (also applies to main DCS menus like Options). For me 1280 x 768 works correctly, but 1280 x 800 I get the mouse error. This is on an ASUS 2560x1440 native res monitor.

And FYI radius area is the square of radius. So if you double the radius, then DCS will need to load 4 times as much data. If you set the pre load radius to 100, and fly low, you will see the trees, etc. get created in front of you. I would expect every different h/w system has a sweet spot for radius/visual appeal vs. air speed vs. stuttering.