Jump to content

TacticalError

Members
  • Posts

    32
  • Joined

  • Last visited

Posts posted by TacticalError

  1. I would absolutely love some infantry improvement. 

    Here is a list of things I would like to see.

    -Better infantry models (I hope the backseat gunners on the hind will look like actual russian soldiers and not whatever the mi-8 ones are)

    -Better animations.

    -Duck for cover under fire.

    -Make them less accurate.

    -Give them actual small arms rounds, not 20mm HE shells.

    -Take more splash damage from HE cannon shells. Maybe if explosions are going off near them their aim would be way off or they would fall over and stand up.

    Also why are there so many tracers?

    • Like 7
  2. Sorry, very dumb question which is probably covered somewhere that I can't find: How do I assign functions to HOTAS controls if the function is not listed in the control list?

     

    I just installed the A-10C II and it changed several HOTAS functions which I want to change back to how they are with my original A-10. For example, CHINA HAT AFT SHORT boresights the TGP on the original and it's LSS TOGGLE on the A-10C II. How do I make CHINA HAT AFT SHORT boresight the TGP on the A-10CII when all I can do in Adjust Controls is assign CHINA HAT AFT to a switch on my throttle and there is no Boresight TGP operation to assign?

     

    Then, of course, how do I assign LSS TOGGLE back to DMS RIGHT LONG? Etc., etc.

     

    And where's Boresight TGP on the A-10C II anyway? I don't see it on the new HOTAS Commands references.

     

    The A-10 hotas functions were changed to a more realistic set of hotas commands. According to SMEs the hotas commands are now like they are in the real bird and there is no boresight function in real life. LSS toggle is now china hat aft short, tms right long now makes previous markpoint spi. It's odd at first, but now I find the hotas commands make more sense and are easier to use than previously.

  3. I made a thread about it on here, I have no clue how to link to it so here it is:

     

    Some explanation:

    -Profiles are per device so you need to create one file for each device.

    -You need to create a separate file for "keybinds" and "axis commands" (I do axis manually, it's easier and you can make sure everything is right)

    -Make sure the correct column is highlighted when saving or loading a profile

    -You can save profiles for each device, then go load them, you don't immediately need to go load it after saving.

    -Name the files so you remember which one it was for example name them "a10throttle.diff.lua", "a10joystick.diff.lua"...

    -You can delete these files after you are done, but I recommend keeping them if you accidentally clear keybinds or reset them to default.

     

    1 Go to "Settings" -> "Controls" select "A-10C Real"

    2 Highlight any keybind under "Keyboard" (So that the keyboard column is highlighted)

    3 Press "Save profile as", name the file and save it to a folder that you can find later (the default one it opens to is fine, it will always open the same one)

    4 Then select "A-10C II Real"

    5 (Same as step 2) Highlight any keybind under "Keyboard" (So that the keyboard column is highlighted)

    6 Press "Clear category" to make sure no keybinds overlap and do weird things

    7 (Same as step 2) Highlight any keybind under "Keyboard" (So that the keyboard column is highlighted)

    8 Press "Load profile" locate and select the file you named in step 3

     

    Done, repeat the process for other devices.

  4. Hi,

    I have seen multiple people struggle with transferring keybinds. Here is one easy and simple way to do it. I believe you can do this via .lua files, but I'm not an expert on those and I'm going to leave that to the lua wizards.

     

    Some explanation:

    -Profiles are per device so you need to create one file for each device.

    -You need to create a separate file for "keybinds" and "axis commands" (I do axis manually, it's easier and you can make sure everything is right)

    -Make sure the correct column is highlighted when saving or loading a profile

    -You can save profiles for each device, then go load them, you don't immediately need to go load it after saving.

    -Name the files so you remember which one it was for example name them "a10throttle.diff.lua", "a10joystick.diff.lua"...

    -You can delete these files after you are done, but I recommend keeping them if you accidentally clear keybinds or reset them to default.

     

    1 Go to "Settings" -> "Controls" select "A-10C Real"

    2 Highlight any keybind under "Keyboard" (So that the keyboard column is highlighted)

    3 Press "Save profile as", name the file and save it to a folder that you can find later (the default one it opens to is fine, it will always open the same one)

    4 Then select "A-10C II Real"

    5 (Same as step 2) Highlight any keybind under "Keyboard" (So that the keyboard column is highlighted)

    6 Press "Clear category" to make sure no keybinds overlap and do weird things

    7 (Same as step 2) Highlight any keybind under "Keyboard" (So that the keyboard column is highlighted)

    8 Press "Load profile" locate and select the file you named in step 3

     

    Done, repeat the process for other devices.

    • Like 1
  5. Flare and chaff buckets not correct

     

    Chaff only dispenses from the right wingtip and the left centerline buckets. Flares only dispense from Right centerline buckets. nothing comes out of the left wing buckets.

  6. You have one of the best computers for simulation, but DCS is very demanding even on the best machines.

     

    I understand that no one spends $ 800 on an RTX2070 to fly with flat shadows.

     

    Even Matt Wagner has MSAA on 2x

     

    The best returns are always obtained with presets.

     

    In my opinion, what kills your performance is MSAA 4x and Ultra range.

     

    DCS is still not very well optimized.

     

    I recommend you try with a preset (high) setting and after that, add things to see what affects performance.

     

    The presets are intended to offer the best balance of performance vs. graphics quality.

     

    I played around with settings more and have gotten to the conclusion that it must be related to shadows, the only 2 things that help with the problem are: Turning shadows to flat (Looks bad but the problem goes away) or turning shadows to medium instead of high, this makes it so the FPS doesn't fall to 30-40 rather 70-80, so it almost fixes it. Rest of it is probably just high detail textures rendering in.

     

    My suggestion in terms of a permanent fix would be to make a separate setting for shadow quality on trees.

  7. It's not what we call lag, but low FPS, to my knowledge it's pretty much normal for many to have half or worse the FPS down at tree level, trees also add burden on the CPU. Vulkan API and Multi-Threading improvements should alleviate this in the future.

     

    As for the shadows being a culprit in your case, it may just be LODs and other things that need adjusting perhaps.

     

    Also you don't have the most beefiest CPU, this sim does require the best of the CPUs out there for optimal performance. The extreme level probably not worth it, but an i7 over i5 is recommended when it comes to Intel CPUs.

     

    But there's one other thing, I found out DCS doesn't support occlussion culling, this means all those shadows and trees that you can't see because they're behind the first line of trees you do see, are rendered fully for nothing, wasting resources.

     

    Point 1: Yeah, english isn't my primary language. What I meant was low FPS/performance, generally when playing games in our group we tend to say "lag" to all sorts of performance issues.

     

    Point 2: i7 isn't the best in all cases... my i5-10600k matches a i7-9700k and can outperform a i9-9900k in some areas... I would say my CPU is on the beefier side of the spectrum.

  8. I get really bad performance when I go low altitude in a forest (as an example just taking a right turn in the F-16 freeflight and going below 600ft agl) I go from 90-100 Fps to around 40 Fps, I belive it renders shadows at insane detail for hundreds of trees. I don't think this amount of detail is needed when flying at 600kts. The lag can be avoided by turning terrain shadows to flat, but that makes the game look really bad in the forests. I suggest an option to choose the distance at which shadows render at really high detail so helicopters can still enjoy beautiful shadows up close. I am not sure if the trees themselves getting higher resolution is a problem, since it almost goes away by turning shadows to flat.

     

    I run a RTX 2070 Super, 32gb of DDR4 ram and a i5-10600k, DCS is installed on a M.2 NVMe SSD.

    Here are my settings:

    attachment.php?attachmentid=243324&stc=1&d=1595613205

    Screen_200724_205256.thumb.png.988863bdc90f8ec57e26472e158c4e17.png

  9. I have had this problem for a while. Basically depending on the time of year there will be a color reflected on the bottom of your aircraft, canopy and hud. In spring the color is green-ish, in summer it is yellow, autumn it's orange-ish and in the winter it's white. Here is a picture of the bottom color in the default time set in Mission Editor (Summer): attachment.php?attachmentid=238462&stc=1&d=1591271066

    This issue is also present when flying low altitude, when over water the issue goes away shown here in this video:

     

    The issue shown in the video is also there in the first image. The issue can be resolved when you are sitting on ground, you need to zoom out in the F2 view then go back in. However, this does not work for flying low altitude.

     

    Here are my graphic settings and special options for the F-16:attachment.php?attachmentid=238463&stc=1&d=1591271907

    attachment.php?attachmentid=238464&stc=1&d=1591271907

    Screen_200604_143505.thumb.png.e7c0fb8b779048e4676853c6296fe364.png

    Screen_200604_141428.thumb.png.a39168c836d3c8a1ed0a61727cb04033.png

    Screen_200604_141451.thumb.png.f348994b8446891b38c3d660a41600a7.png

  10. For anyone who wants to remove the tint here is a small description.lua - simply extract and drop the folder Cockpit_F-16C into your SavedGames/DCS/Liveries.

    No other changes are needed and it passes IC.

     

    I also hope there will be a special option between 'tint' and 'no tint', that would be the easiest...

    I can't get this to work...

  11. Hi,

    I am most likely going to pre-order the F-16 in the coming days. I would like to know a few things about it!

     

    -If the Sniper XR is not available, which Litening variant are we going to see?

    -What kinds of liveries are planned for it? (Any tigermeet type liveries, or are they all going to ke AF standard?)

    -Are there any plans for triple racs for the mavericks or dual racs for A2A missiles?

    -Are there any pictures of the interior cockpit panel lights?

    -Will there be a IFF function on release? (If not, when will it be available)

    -How powerful of a radar does it have? (How far can it see and lock targets?)

    -Is Wags going to do a video tutorial series on it? (I find them super useful!)

    -What will the power to weight ratio be compared to the hornet?

    -Will the JHMCS be able to interact with the targeting pod? (Even if its Litening or Sniper?)

     

    I will most likely pre-order it no matter the answer! :pilotfly:

  12. As soon as the pilot is in the cockpit and strapped on it will be retraced by the ground crew. And as long as the engines turn the ladder cannot be lowered.

     

    I mean, it would be nice to have but if you want to be realistic you could only see the ladder down when you shut down the aicraft...

     

    Exactly how I want it! (I guess it would be nice to see it being able to be lowered until you turn on apu or something?)

×
×
  • Create New...