Razi

Does rendering a second monitor with a second gpu improve FPS much?

Bankler, thanks again for all the work put into the mission! I see that you've added glideslope when your in the groove, but I'm usually a bit preoccupied in that moment to really check it. Would it be possible to have that info included in the summary? Also, I already asked you about time in the groove on Discord, are you still considering adding that info? Thanks again!

Yes, love the update!

You might be interested in this thread Jar: https://forums.eagle.ru/showthread.php?t=225991 Matt has put quite a lot of work into the Carrier landing geometry and IFLOLS as implemented in DCS.

Thanks for the post! Do you still use the Samsung Odyssey anymore?

L-ALT + C activates "mouse look" in clickable cockpits.

This is so true... I can't fly without FFB anymore, but it has enough issues that I've slowing been trying to re-engineer it. I'm currently using just the gimbal from the MSFFB2 while the stick from a different stick.

I've been chatting a former F/A-18C pilot recently (he's somewhat known here) and we were talking about the FCS, trim, self-centering joysticks, and FFB. He occasionally plays DCS and has tried just about every consumer stick/throttle out there and ultimately decided to make his own stick because nothing out there (that he has tried), but the pressure sensors sticks behaved anything like the real aircraft, especially when it came to trim. So he uses a force sensor stick because the spring joysticks just throw his muscle memory off too much. After talking with him, it became clear that the FFB sticks with proper FFB implementation were working correctly and this is what he thought was essential to flying properly, especially when trimming the aircraft. Anyways, proper FFB implementation is my most waited for "feature" so I was motivated to cast another vote for this!

MadDog-IC fixed many of the problems with the missions and campaigns. Here is his single missions: https://www.digitalcombatsimulator.com/en/files/2459240/ As for the Kab500kr, it still misses, but I've been able to hit the targets by simply dropping the bombs without a lock. To do this I have to decrease the target size box small enough so it doesn't lock. However, my wingman still can't hit the targets with the guided bombs, but will hit them with dumb bombs. So give him dumb bombs and use guided bombs yourself.

I like to have a custom CameraViewAngleLimits as well, but there is a problem with editing that file. The issue with editing that file, which I've been trying to get around, is that your client will fail the integrity check for multiplayer. So that may be a concern for some people. I haven't figured out how to adjust the parameters in that file that don't exist in the SnapViews.lua and still pass the integrity check.

I had a similar problem recently. You should try setting a snapview in-game (RALT-Num0), then close the game. This creates the SnapView.lua file if it doesn't exist. In my case, the file existed but was out of date and didn't include the F/A-18C. Doing this updated the file.

For completion sake, I found the solution. My SnapViews.lua in "Saved Games" was out of date and didn't include an entry for many modules, including the F/A-18C. I needed to create a new snapview in-game using RALT + Num0 (I had never used snapviews) and this updated the SnapViews.lua with entries for all the remaining modules. This at least helps me set some of the view parameters I like, but doesn't allow me to modify the zoom limits unfortunately.

I found the issue. I just had to save a snapview ingame (never used it before). Now all the modules have an entry. Thanks for triggering some new ideas for me Rudel_chw!

For the F/A-18C? They work for all other modules, just not the F/A-18C. There isn't even an entry for it. Did you create one? I haven't tried that.

The F/A-18C module no longer uses the snapviews file as all the previous modules and currently the only way I can adjust the view is through the view.lua under the module in the root directory. This causes multiplayer integrity check to fail though. Does anyone know how else this can be done so as to pass the integrity check? I have a dual monitor setup in a vertical orientation, they are two different sizes/resolutions. As a result I need to slightly adjust the default view angle. I also like to adjust the maximum zoom limits as I toggle the zoom, rather than use an axis. Thanks, Razi

I guess it is time for a friendly reminder! I can't fly the Su-25T with this bug! It was one of my favorite modules to fly... The autopilot is just such an important part of flying this aircraft.

Is it still not possible to have a modified view for the F/A-18C and pass the integrity check? I'm looking forward to the Blue Flag campaigns, but unless I can have the view setup properly for my multi-monitor setup, it is unplayable for me...

Regarding the deadzone, there seems to be a software/firmware built-in deadzone. I've included a gif of the Y-axis where I am moving the stick smoothly through the center, with forces off, which reveals the deadzone as a slight pause in the movement of the indicator. I never stop moving the stick. I am attempting to figure out how to reduce or remove this deadzone to stiffen up the sloppy play at the center. I'm considering the same bypass solution that @sydost posted that would help DCS receive a smooth input, but the center area of the stick would remain sloppy still. Any ideas? What I currently do in-game is trim the center away from the center point of the MSFFB2 and this creates the nice stiff and precise control/feeling that I'm wanting at the center. However, I run into issues with this method in the F/A-18C during landing as trimming to on speed moves the stick to the sloppy center area.

I don't think these are the actual questions in practice. Updating frequently (even daily) is a norm in today's online world. I am also probably not alone in being a user who uses the open beta exclusively, yet has never reported a bug (I'm not knowledgeable enough to differentiate between features/bugs...). The release version still has bugs and in general the open beta is remarkably stable in comparison to release. I think also there is a general (not unanimous) acceptance that a simulator is vastly more complex then most other entertainment software and subject to many bugs. Plus DCS is always evolving and in this way, release functions as a "beta" anyways. Personally, I love it this way. Far better than going from Flanker 2.0 to LockOn to FC series, etc., in discrete stages. I think in practice the two primary questions for choosing release vs open beta are: 1. Do you want to fly multiplayer? 2. Do you want the latest features/modules? If you answer yes to any of the above, open beta is for you.

Has anyone looked into exporting the inflight idle and AB retractable detent positions? I'm trying to add these features to my throttle (diy). I had thought about using other data, such as the rad alt in combination with other info to extrapolate the needed info to roughly simulate the retractable detents, but then I discovered in the NATOPs that the inflight idle detent may retract during high G maneuvers allowing the throttle to be moved to the ground idle position, so a direct export would be more ideal, if possible. Thanks for any help!

Is there a way to export the retractable inflight idle and carrier launch AB detents? I have the ability to add these features to my throttle. I was going to use the activation parameters detailed below to extrapolate the required conditions, but then I read that in high G maneuvers, the in-flight idle detent may retract allowing the throttle to move to ground idle. So, it seems an ideal solution is to have the retractable detent data exported directly. From Natops:

Do you know if it is possible to export the retractable idle and AB detents?

I was wondering this, as I already have one of the four. Thanks NineLine!

Recent flight stick poll suggests their is still a fairly substantial group using force feedback sticks, so maybe one day we'll get this one sorted. :music_whistling:

Still holding out for this! Maybe it is futile to wait, but I enjoy flying the Su-25T, even more now with the FFB stick. I have yet to make it all the way through the campaign without issues, I remember there was someone who updated many of the missions fixing many of the bugs. Hopefully they still work for 2.5. I think they also worked out some of the problems with the single missions too.