Caldera

Hey All, As I am acquiring more and more DCS aircraft modules I have noticed something vastly different in the canopy modeling. Where I should actually post this thread is unknown to me. This is the A-10C ii (I am running Taz's canopy mod which I believe just removes the yellow tint) The canopy is clean as a whistle This is the AV-8B This is the F-16C OK... I could go on and on. Sometimes these canopy effects are so extreme I can not see didly as the entire view point is blanked out like some one pulled a plastic bag over my head. For reality sake or not, either way I don't really like this effect. I much prefer the clear canopy of the A-10C ii. I do not know which is more true for the A-10C ii: Canopy effect is not modeled Pilots visor effect is modeled For the other aircraft, I think that these canopy effects are beautifully modeled and that the effect is absolutely stunning. And to me, they seem very very realistic if I were a camera sitting on the pilots shoulder (YouTube videos). However, this is not the case, as I am indeed simulating that I am the simulated eyeballs of a simulated pilot viewing the world through a simulated helmet visor or even simulated aviators glasses. Is there an option some where to do away with this effect or do I need an aircraft by aircraft mod of some sort? Thanks in advance, Caldera

Hey Guys, Sorry for taking so long to get back. I had issues with my joystick and I ended up doing about a 100% reconfigure. I am learning to adapt better, but I still have not solved my yaw issue. My landings are generally controlled... This first picture has no pedal input. (well maybe a little, my left foot must be a tad fatter than my right foot) This second picture does have pedal input. To maintain co-ordinated flight I am adding quite a bit of right pedal. Should I just ignore the yaw? Caldera

Thanks Guys, OK... So for landing I have been coming in at 40-60 knots and dropping at probably around 500 FPM. To stay coordinated I find that I have to add more and more right pedal. At times I am at or close to full right deflection on my rudder pedals. This doesn't seem quite right to me because I just about lose all ability to rotate any more to the right, all the effort just goes into flying coordinated. I get the part about left pedal counter thrust below ETL, but that is less than 50% of how much right pedal I am adding at 40 kts. I am using a straight curve on my rudder pedals. I do not have a good feel for descent angles so I use forward speed and vertical air speed as my guide. What descent FPM and forward speed should I shoot for? Also the dang pilot trimmer causes me some issues. If I do not use the trimmer then my joystick becomes a beast to hold in position. I have the weakest springs and a cosmo cam installed. The biggest hindrance seems to be how coarse the Cyclic controls are. I am using the ones in the picture below. J Just a quick flip of the switch can cause pretty severe gyrations to occur due to how much the trimmer effects control. Is there a way to tone down how much these controls effect the pilot trimmer or are there other controls some where else for finer control? Maybe use another joystick with no springs installed? Caldera

Hey All, Go easy, I am a new pilot here and not a whole lot of sim rotary wing experience. I bought the UH-1H module so that I could practice for another rotary wing module that I have pre-purchased. Still waiting... I think that I have a handle on VRS (and crashing), entry and exit to and from translational flight. But, I do not get a couple of things. Other than YouTube (Casmo among others), I am self taught. So maybe I am doing it wrong. As I am coming in for landing I am working the forward trim off as I descend. I suppose that I am in sort of an auto-rotation mode, but with more collective angle. As I slow down, descend and re-add collective I also have to start adding right pedal. The faster this happens the more right pedal I have to add. If I go too fast then I am pushing almost full right pedal. Is this correct? As I slow down for landing I try to be pretty close to being inside ground effect by the time I get below 40 knots. If this happens when I am too high then I try to go into an outside ground effect hover and lower myself down slowly. But I notice something kind of weird happening. I find it somewhat hard to slow down to 40 knots. It takes me awhile to do that. As soon as I go below 40 knots its like the Huey hits a truck runaway ramp of some kind. The rate of speed decrease goes way up. So typically, as I am gliding down using more and more right pedal. Then I go below 40 knots and the thing hits the brakes and speed drops rapidly to, lets say, 20 knots along with some dash shaking. Now I have to slam the left pedal or it starts a merry-go-round routine. Is this correct? It does not make sense to me that this is the way it should be as it sets up for quite a bit of instability going rapidly from right pedal to left pedal, but I am uncertain. Thanks in advance, Caldera

Hey All, This is a snapshot of the Persia map flying in the Huey. The Huey is typically the lowest load on my GPU, and notice that it is only running at 49%. Both cores are getting hammered and very often I see spiking to 100%. Both cores are always running at 4.606 GHz when I check them. The FPS was very steady with no stuttering. I do not know how close my PC is to CPU saturation running that mission, which is just flying to the west coast from Ras Al Khaimah and then back again. Caldera

Oko One thing that I just did notice that has changed, it is that the stutter I was getting at Creech is gone. Taz, More than 2 cores or more than 2 logical processors? My system always seems to use only two cores / four processors. With exception of a few ripples at load time, the rest are "bored". Caldera

Salsa, For CCRP, are you making sure that the target you intend to bomb is also the SPI? I do that occasionally where the TGP is on the target I want to bomb, but the SPI is on a Mark or Steering Point (some where else). The fall line is calculated to the SPI. Check by making the sure that the TGP is SOI then TMS Fwd Long to make sure the TGP is SPI. Posting a short mission track would help out allot. Caldera

How about that! Caldera

Uri, In addition to the comments above, I often hook my current SPI. With the TAD in EXP1 mode and the SPI centered on the TAD. I adjust the TAD range so that the plane symbol is always on screen. The yellow dotted line of the hook always provides an easy visual reference as to which direction the SPI is compared to where I am at and which way or how much I need to turn to engage. It helps tremendously with my SA. Caldera

Hey All, With version 2.7.10.18996 I tried out the HMCS keybinds. The only one that I can bind to the keyboard is HMCS Power ON/OFF. Working as intended? Caldera

Oko, I could not notice any difference with Hardware-Acclerated GPU scheduling on. Caldera

Jonsky, Thanks! As always, you are a saint. I suspect that it is going to take me awhile to digest all of this. Caldera

Oko, This was taken using my FPS test mission. Basically, an A-10C at tree top level with the TGP on. It is near Senaki. The FPS was rock steady. I do seem to notice CPU bottle necking at times on my system especially near airports. Creech is one such example and it is a CPU nightmare. If I turn my cockpit view using TrackIR, moving from extreme side to side, I will always get a stutter right at the canopy frame. I notice the FPS drop significantly for just a moment at that same instant. I am almost positive that it is not the GPU as it would not be loaded over 75% when that occurs. I see the CPU spiking to 95% or more until I get a ways from the air port. Then everything just smooths out. Caldera

Thinder, In my PC I have: 64GB (32GBx2) DDR4 3200 CL16 Crucial Ballistic Some1, Thanks! From above BB stated "DCS is currently only loading two cores, sound on one, and "everything else". I am only wondering how true this is. The sound should be a relatively low usage and should be almost constant. For example, steady state flight would always be the same. That is if I am correct. This is not what I see. I see both cores usage values change with the reaction to different missions configurations, maps and multiplayer etc... I just have to wonder. Caldera

Deano, OK I had not considered altitude much. My F-16C AAR training mission is a hold over (save as) from my A-10C AAR training mission. Both are at 15k. For the F-16C I kicked the speed up to around 313 IAS for hook up. I will test at a higher altitude. Caldera

Thinder, Not sure I understood most of what you stated. My apologies, I do not have the background. I was not my intention to paint with such a fine brush that you might do. I would use a much larger brush with big sweeping strokes. I was my intention to illustrate a point of discussion from an altitude of 5000 AGL. Just, because I found it interesting. With 8 cores, only 2 are used and the processors alternate usage Where in the past I had read only one processor was used by DCS and it did not seem quite right to what I had observed myself. Caldera

Deano, Thanks! OK Gas Station? I have never heard of it. The Wake Turbulence (WT) is not severe where I am hitting it IE there is not a sudden and forceful rolling effect. However, just aft of the nozzle there is a WT effect, I call "The Hump", that causes quite a bit of lift. It has a fairly severe onset and offset just about as I get to the nozzle. When I watch IRL actual refueling I try to notice this. I don't see the same effect going on, but that doesn't mean that it isn't. In the A-10C I generally just plow right through it. Caldera

Deano, Now that's funny! Seems so easy put in the right perspective... Jay, I did put my resolution back to 2560x1080, I realized that had to give too much of the rest of the game in order to do this one thing. I did set Anisotropic Filtering back to 16x and the PDL' s are much clearer. I can realistically only run MSAA 2x and no SSAA. I always fly with Wake Turbulence on. The F-16C seems much more reactive and harder to control in punching through "the hump to the nozzle" than the A-10C is. The AAR videos I have watched show the F-16C pulling up to the nozzle (as in the A-10C), waiting for BODO to react and then slipping forward just underneath to the left or right of the nozzle. It does not seem like Wake Turbulence is effecting their flight much and I do not know if it is actually on or not. I have generally been trying of late to approach the nozzle a bit lower beneath it, then waiting for BODO to wake up, then slipping forward to the right PDL and then coming up to the left PDL. This makes it harder for me to re-orientate under the tanker, but reduces the porpoise stabilization dance with the stick. Sound about right? How do you guys deal with Wake Turbulence? Caldera

Hey All, This is just a point of discussion. I do not know if this is a bug or not. The below pictures were taken from Anderson AFB on the Marianas map while taxing to a runway. I do not know the range to the cranes, but they are fairly close. No zoom: A little bit of zoom: A little bit more of zoom: I am bringing this up because I noticed this for other things as well. For example, while landing at night, the Anderson AFB the runway lights are not visible unless I zoom in. The effect is the same as the cranes pictures I have shown above. Certain things remain invisible unless zoom is used. Changing the Visible Range to Extreme does not seem to make any difference. Caldera

BB, Thanks! For the record CPU 15 was not MIA and is in fact present. I did not set up the display correctly. The picture below was taken while in a MP server ready for take-off. Caldera

Hey All, I recently started monitoring CPU performance "Just to See". What I noticed is kind of weird for the unknowing and unaware. This is my CPU: Processor Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz, 2904 Mhz, 8 Core(s), 16 Logical Processor(s) These are two different screen shots I took with in a few seconds of each other. I can't explain why VRAM changed by so much, this does not seem typical. So, just take a look at CPU usage for now. While playing DCS there seems to be only 3 processors (CPU's) that ever become significantly loaded. These are the 13, 14 and 16 CPU's. CPU 16 is the most consistent and usually maintains around 30-45%, but can spike higher or lower. CPU's 13 and 14 are like Peter and Paul. When one goes up the other goes down and vice versa. They swap usage on a very periodic basis. The highest spikes by all the CPU's occur while the game is loading. Another screen shot shows that CPU 15 is completely MIA. Of course that make complete sense. Not... From what I do understand the Cores are hardware and the Logical Processors (CPU's) are software. I am only guessing that CPU 13 and 14 would be using the same core? What goes on with CPU 15 and 16? This behavior only isolated to DCS or do many applications operate this way? Caldera

Aries, I just increased my DRAM. Below is a screen shot using MSI Afterburner while on a MP server after some play time. The first number by RAM is the allocated amount and the second number is the usage amount. I have my FPS capped at 50. I think... I noticed almost no stuttering. With 16 GB DRAM, I typically noticed allot of stuttering specifically right after entering the server. But my FPS could also go in the crapper at those times and be very unsteady. After a while on a MP server the stuttering smoothed out quite a bit, but never really went away entirely. Caldera

Dokken, You can read through this thread, I was wondering about the same things as you do. My 32 inch main monitor can run at 3440x1440 @ 144Hz. For DCS. my overall resolution, with two screens is 2560x1848 (2560x1080 + 1366x768). I run at 2560x1080 on the main screen for fidelity vs FPS reasons. I find the display to look "good enough" while maintaining around 60 FPS. I have to really look to find differences between 2560x1080 and 3440x1440, but you can see them. With the higher resolution, for less demanding games, you will love this monitor. I am also pretty sure that DCS will whittle your FPS down close to single digit numbers at times with any more than just a couple of settings above the lowest possible. I believe that it also possible to run DCS at, for example, 3440x1440 even the your monitor is capable of 5120x1440. You would have to edit the MonitorSetup file to get DCS to center on your display. This would not fill display and you would have borders on the sides. Caldera

Marc, I figured out my problem with Taz's help. All I had to do is restart DCS after changing the setting. I had not been doing this before. I do use Sharpness, I have not tried changing DSR. Does it impact FPS? I use no special software. I have a custom view file that I have used ever since I wished to have the MFCD's off the main screen for easier viewing. It is relatively easy to do and it is a part of DCS. Let me know If you would like advice or a copy of my MonitorSetup lua file. Some specific set-up is required. My MFCD monitor is very crisp and is a 16 inch flat screen. The TGP view is as good as DCS provides. I did change the resolution to 1366 x 768 for a test. There does not seem to be any visual difference in the DCS TGP MFCD display between 1920 x 1080 and 1366 x 768. I am also running fewer pixels through my GPU that helps FPS just a small amount. I can also read the text much easier for other applications I might use the monitor for. Caldera

Hey All, I just got the ACE Flight Rudder Pedals. I adjusted them for comfort and then plugged them in to my PC. I tried to calibrate them. The first thing that I noticed is that The Virpil Configuration Tool recognizes them, but I can not calibrate them. I thought this was weird. On the line for the for the pedals it says "Version not Supported" for firmware version 20211101. The Virpil web site does not detail how to update the firmware or if I even should / need to do so. At least where I can find any information on their web site for the pedals. The firmware that I have installed on my Stick and Throttle is 20210102. The latest firmware version I see on the Virpil web site is 20201118. Confusing... I have had a couple of problems with the pedals: In DCS, I could not get the left and right to work correctly at first. The DCS rudder would always go the opposite direction of the actual pedal movement even if I inverted the axis. I finally discovered that there are actually two axis that can be selected on the DCS Controls Adjustment page which are the RZ and the R axis. The default was RZ and I switched to the R. That fixed the problem, but I never noticed multiple axis selectable for a single device before. Windows Control Panel tester chokes on the them. The pedals are visible under Hardware and Sound. If I right click on the pedals and then select Game Controller Settings then select VPC Rudder Pedals then select Properties I get a Game Controller error. The error says "Your Game Controller is not connected correctly. Please verify that it is plugged in to your computer". That is just dumb, because the controller (pedals) is (are) working in the VPC Joystick Tester and in DCS. Suggestions? Do I need to update the firmware? Don't worry be happy? The pedals are great and so far I love them. Thanks in advance, Caldera