pdmarsh

@Floyd -- Thank you for responding. I tested this with MSI Afterburner disabled, so that particular profile would not have been running. Also, I have this issue on three separate PCs, all running with and without Afterburner. There has to be a reason for this, but I am running out of things to check. During the session associated with the graphic I posted, DCS was all but unplayable. I can usually live with it, but that one was pretty bad. Thanks again, Paul

@Nealius -- Thanks for responding. So far I have not seen any trigger or any pattern at all related to this, but I will continue to look for some common thread. Paul

For over a year I have been living with, and trying to isolate, an in-game stutter issue that I experience when flying DCS. Thinking it was related to external hardware, I completely isolated all external inputs going into my PC, including Ethernet and speaker connections, and still experienced the problem. Since none of the folks I fly with seem to have this exact problem, I assumed it was not related to DCS directly. However, I do not see the same issue when I fly X-Plane, although I do get an occasional stutter there. I also thought it might be the PC itself, but I recently built a new one and have the same issue. Finally, I thought it could be our home electricity. I ran DCS on my laptop on battery power and still saw the spikes I will mention below. A test device showed no problems with our electricity. I also made sure no scripts were running and still saw the issue. One final oddity about this is that when the stutters occur, DCS apparently rescans my input devices and resets anything not currently in sync with the sim. I see this mainly with zoom when my zoom lever is not synced with the default view. If I am in default zoom in-game and one of these stutters occur, my screen view will jump to whatever the input device zoom lever is set to. In fact, I originally thought I had a bad controller way back when this issue first appeared. This rescan of input devices has occurred on two PCs that show the stutters and with different controllers. Each of the spikes seen in the attached MSI Afterburner chart (“GPU usage” mainly, but also in “FB usage”) coincide with significant on-screen stutter. In this case they were coming at the rate of every 20 seconds or so. When I have this issue, it isn’t always as regular, but usually it is fairly regular. However, there can be sessions when I have no MSI spikes or on-screen stutter at all. It can happen in single or multi-player mode. It happens with different modules. The stutters themselves can vary in intensity and sometimes I’ll see the MSI Afterburner spikes but not have on-screen stutter at all, but this is somewhat rare. I even thought that MSI Afterburner itself might be a problem, so I ran DCS with it completely closed, i.e. not running in the background, and still had on-screen stutter. If anyone has any idea at all as to what the root cause of these stutters might be, that input will be greatly appreciated. The following systems specs relate to the PC that produced the attached MSI charts. DCS Version: Currently running 2.5 Open Beta but have had the issue in 1.5 versions as well. Windows 10 - 64-bit GIGABYTE GeForce GTX 1080 Ti 11GB 352-Bit GDDR5X PCI Express 3.0 x16 ATX Video Card Intel Core i7-7700K Kaby Lake Quad-Core 4.2 GHz ASRock Z270 Extreme 4 LGA 1151 Intel Z270 HDMI SATA 6Gb/s USB 3.1 ATX Motherboard SAMSUNG 960 EVO M.2 500GB NVMe PCI-Express 3.0 x4 Internal Solid State Drive G.SKILL TridentZ Series 32GB (2 x 16GB) 288-Pin DDR4 SDRAM DDR4 3200 DCS log file attached. Thanks, Paul dcs.zip

@Capt Zeen -- It turns out that the VVI data in the Ka-50 is linear even though the gauge itself shows a changing scale. The following formula works pretty well. (VARIO_SPEED*0.0009155)-30 This formula will show whole numbers only, e.g. 1, 5, 10, -20, etc. So, for most of the range from 1 to 2, for example, the display will only show 1. If you want better resolution, you can use the formula below to add a decimal place. However, no dot will appear on the display and anything from 0.1-0.9 will show as 1-9 on the display. 1 will show as 10, which really means 1.0. It's probably not worth the confusion, but here is the formula. ((VARIO_SPEED*0.0009155)-30)*10 Finally, the only display on the Multi Panel that will show the minus sign for negative numbers is the one labeled "VS." I hope this helps. Paul

Hi Capt Zeen, I'll take a look at this tomorrow and see if I can come up with a formula that will at least be close. Formulas for nonlinear scales get fairly complicated and might not work well directly in DCSFP. Paul

Thanks everyone for all of the great input. Since this does have some visibility now, I guess it doesn't need to be moved to the bug section, which I was coming on-line to suggest and saw it had already been mentioned. Paul

That captured it quite nicely. That's the exact effect I'm getting with differing approaches. I actually hope it's a bug, because so far I can't re-master precision bombing (not that I was ever actually a master). Thanks, Paul

I am curious of anyone else has seen this or something similar when using precision bombing mode. I used to be able to get into a fairly steep dive, line up my target and get proper HUD symbology all the way down to the release cue. Now, whether I try a steep angle, shallow angle, fast or slow, the symbology drifts below the HUD before the release cue occurs. Pushing the nose down does not bring it back. I'll practice more, but maybe something did change and/or is actually broken in the module at the moment. Thanks, Paul

I'm glad the profile is helping a little. Regarding the Multi Panel configuration, my P-51D profile was made prior to a significant change in DCSFlightpanels. Before that, the Multi Panel could have only one configuration. Now, the buttons and displays can have multiple profiles depending on the position of the selector dial, i.e. ALT, VS, HDG, etc. Unfortunately, earlier profiles have to be redone for the Multi Panel. I don't know what might be wrong with the display. I tested this last night with the P-51D and did not see any problem. I put ALTIMETER_VALUE in the upper LCD display while in ALT mode as you did and it reported the proper altitude throughout a wide range. You might try testing this with another module and/or another value, e.g. engine RPM, to see if proper data is being displayed. If not, you might try reinstalling the device driver (I know, the standard response :)). Unfortunately, not all DCS-BIOS module profiles have built-in formulas to convert raw data into meaningful numbers. That was something we started to do with later profiles. Depending on which module you test with, you might have to use a formula. Paul

HI og_wolf, I have attached my P-51D profile. You will have to change the hardware IDs in a text editor to match your own panel ID numbers. I don't recall how well I labeled each configuration, but there should be some indication of what button or switch does what. Let me know of any questions. Thanks, Paul P-51D.zip

Sorry for not responding sooner. I'm afraid that I was not able to reproduce the problems you are seeing. Hopefully, the log files you are providing to ArturDCS will help get to the root of the problems. Paul

While ArturDCS is working on the M2000C, I'll begin work on a DCS-BIOS profile for the Harrier. If you have the means, please do support ArturDCS with this work. I fly the modules, but his love is the software. The cost of the modules adds up. Thanks, Paul

I did a quick test and the Radio Panel worked as it should in DCS 2.5 in an A-10C on a PC running Windows 10 and with the Thrustmaster Warthog HOTAS running as well. Paul

Possibly. I'll try to do some testing this evening. I just finished installing Logitech and Thrustmaster Warthog drivers and DCS 2.5 on my new rig, which runs under Windows 10. Paul

Deleted post--irrelevant info after thinking about it regarding the radio panel issue. In case my post got captured in an e-mail, I was thinking I ran 2.5 under Win 10, but that's on my new PC which I have not put into service yet. Paul

@alonpet -- Please try this formula. It applies to the pilot side pressure altitude adjustment. PALT_PRESS*0.004425116+2810 Let us know how it goes. Thanks, Paul

@alonpet -- Let us know if that formula does not work. I'll have to do a little testing, but I should be able to come up with something as well. Thanks, Paul

Yes, I had a feeling it might be something that we just have to live with. It was fairly easy to fix. Thanks, Paul

Hi AbortedMan, It's true that exports have to be enabled for DCS-BIOS to work. However, DCSFlightpanels and Logitech (formerly Saitek) panels can still work as keyboard emulators with limitations. Without DCS-BIOS, the Radio Panel will not function and Multi Panel displays can't be used. However, the Switch Panel, TPM Panel and Multi Panel buttons can be used in keyboard emulation mode with DCSFlightpanels. Also, I fly multiplayer almost exclusively and we always enable exports. Other things have been put into place to discourage cheating, at least in some cases. For example, TacView has a 10 minute delay mode that allows exports and stops cheating. I hope this helps. Thanks, Paul

The attached mission had been created in a pre-2.5 DCS version and then imported into 2.5. Although the ramp parking assignments appear correct, or close to correct, within Mission Editor, when you click on them you will see PRK assignments completely different, e.g. a plane that appears over parking space 2 is assigned PRK number 32. Many are simultaneously assigned to PRK 40. While trying to correct this, I noticed that spots with no plane over them, e.g. parking space 1, are not available in the PRK selection list. The drop down list seemed to change during the editing session in that many available spaces simply disappeared from the list. Closing and reopening DCS brought the list back into shape. Hope this helps. Thanks, Paul ParkingSpace.miz

I'm really having a bad day. I check a few pages before posting looking for status, e.g. module details page. Completely missed the page on the link above. I need coffee, or something... Thanks and sorry again. Paul

Correction I need to correct my comments above. I rechecked my options and found that FFB had not been disabled. The sliders on another page were set to 0, but "Force Feedback" was still enabled in the options. Unchecking this greatly improved handling. Paul

Carelessness. My apologies. Still, thanks for the update. Paul

Posted to wrong forum. My apologies. Paul

This has been an interesting thread to read. I, too, have been having trouble flying the Gazelle in 2.5 after having gotten comfortable with it in previous builds. I know that 2.5 itself is not the issue, but it's been a while since I have flown the Gazelle and am just getting into it again now. Unless I'm mistaken, I think the Gazelle flight model and gone through a number of stages. I have had the module since release and initially the bird was very hard to master, but I did seem to get it under control. At some point there seems to have been an update and it got even easier to fly. Maybe I just got better, but I think the FM changed. With this latest release, though, it's a different bird entirely. I simply can't fly straight and level without a great deal of difficulty. I don't know if magnetic trim ever worked for me, but it does not seem to have any effect now. I saw a video on YouTube where the guy said to not use it unless you have FFB. I do not have FFB, so maybe that's the problem. FFB is disabled in the configuration. From the release notes, it appears that we can expect a fix to a roll problem. I really have trouble holding a roll angle right now, so this is good news. I don't plan to give up on the Gazelle, but something sure seems to have changed. Maybe it's more realistic, but it seems a bit harder to fly than it should be. As an aside, either the HOT missiles are less effective, or my targets have gotten harder. I am trying to update an old mission to 2.5 and one HOT missile would take out a storage tank. Now, even after two or three hits the tanks remain after a bit of fire burns and then goes away. Thanks, Paul