RuskyV

Could be something to do with the creator texture they are using. Proberbly a gazillion GB in size

An option in the menu for reduced G effects would also be nice, you could have the audio and a little reduced vision around the edge but never black out.

I think different hardware combinations available all have their own characteristics having their own role in the experience, using the FSSB R3 force sensing stick has the benefit of extremely good resolution and with no in game curves applied allows for a very accurate way of pulling and maintaining G-force. Before I shelved out on the R3 I was using the warthog base and the experience is vastly different between the two bits of hardware. I don't think there is right or wrong..

I think it should also switch off the radar altitude if already toggled on?

If the junction has been created then you need to cut and paste the contents from D:\DCS.Openbeta into DCS.Openbeta.new When you double click and open your original D:\DCS.Openbeta folder it will open as normal showing the DCS files, this shows that the folder junction is working. Hi There!, I have the same amount of memory as you

I originally started using the symbolic link purely for the scenery textures on the Syrian map which I noticed some of the files in there were being access many times over, I then assumed that those files were being committed to memory for faster access in windows. Thing is DCS already commits these files as textures in memory so when windows takes that same file and dumps it in memory it means it’s using either memory or possibly a pages file. by stoping that process from happening CPU and memory get a break from juggling these large files. I then did the same thing for the cockpit textures because I know these are stupidly big files, when I did it I instantly noticed that these textures were loading a lot faster with no delay and with much better performance when panning around inside. As I experimented further I got to a point where I thought why don’t I just do this for the whole damn folder that contained everything, results were faster loading cockpit textures, less micro stuttering and a more consistent frame rate. As mentioned before mileage may vary but I’m happy with what I’ve seen.

I don’t have the steam version however I can’t see why it wouldn’t work, you would need look at were the root install is and work out where you want the symbolic link.

This is what I did (reference to the original post) and it seemed to make a difference so I put together a really rough guide on how to create symbolic links. I started with just texture files and saw some small improvements with certain modules but decided to see what happened if I did a symbolic link for the whole DCS root folder. I never did any formal benchmarking as this was a personal endeavour and I was going purely from what I observed and felt, however the theory behind the test was to prevent windows from committing large commonly used files constantly being accessed and forcing them into memory along with DCS, the theory is to clear memory for DCS related textures and background files being used for the DCS program. From my understanding how windows was designed was to allow commonly accessed files to be committed to virtual memory to facilitate performance especially for large file manipulation, however this can be problematic with games using considerable amounts of system memory for textures. By moving files outside the program executable but maintaining the path tricks windows into thinking that these files are no longer being commonly accessed thus freeing up memory purely for DCS without interference from windows. This was especially noticeable with the Syria map and its large densely populated urban areas as well as some areas of trees and vegetation, other improvements I noticed were modules added into the scenery with complex textures, (large texture files being accessed many times by windows). My goal is to see if I can get a consistent smooth experience across both single player and multiplayer scenarios, I want to mention this is based off my own in game graphics settings so take into account all variables from system to system. However I was quite surprised... I originally put the guide together for squad members and my own personal use if you find my guide confusing google Symbolic links and read up on it. Hope this helps How to Create a Symbolic link for DCS World.docx

Could it be a wrong calculation in the fuel balance?, I know there is a certain tolerance in the Forward/Right and Aft/Left fuel split before there is a change in CG. The way the fuel is laid out in the F16 could be something to do with balance. There is an engine feed switch in the cockpit that allows you to manually draw from different tanks in order to correct for CG change if required. Might be a calculation error in fuel balance and feed, could explain the left/right tendency if there is no reaction with large throttle changes.

You could in theory set up a TGT to VRP from a given steer point and use this as an add hoc type of visual wind indication in the HUD. Making a run in to target with the CCRP bomb fall lined up close to the VRP diamond might give you rough indication of wind direction. However I've never done this myself...

I think you can reference the F10 map for the coordinate format, at the very least it will say if it needs to be west or east as the second line.

Hi @Doc3908 I'm by no means an expert and I am constantly learning under the same situations shown in your video, however a few observables worth noting. Your turns inside the bandit are extremely tight pretty much cutting across the circle, you need to aim to fly into the Bandits control zone by observing when the bandit initiated his turn and then try to fly to that point in space and time and then making the turn. Assuming the bandit continues to turn you want to make your bid to lag and hold him about 30deg above the HUD on the lift vector, when the situation develops to the point you think you are ready to make a shot pull the bandit into the HUD for a guns kill. -Timing is everything, a pull to guns kill can expend a lot of energy (airspeed) the slower you are the more the leading edge flaps will schedule adding drag as it tries to gain more lift while AOA increases. -Turns made across the circle also close range rapidly ending with very high crossing angles and a risk of overshooting, pulling harder will give you a snap shot at best and not a good tracking guns kill. Judging when to cash in speed for nose position is a skill born out of repetition, it matters less about speed and more about recognising when to exchange energy for nose position in order to employ weapons. Reacting to airspeed changes made by a bandit sometimes leaves you outside ideal performance envelope's so sometimes you have to work what you got. The "when" is sometimes more important than the "how fast" being the difference between a snapshot and a good tracking guns kill. Don't get to hung up about airspeeds. I'm still learning this myself...

As the title says, when selecting the master arm switch to SIM there is no HUD lettering for that status. if intentional then please disregard

I'm not really up on my science but i would assume you could have that amount of weight while not being drag inducing as pylons seem to have a very thin front to back profile.

Thanks for the mission, ill fire this up tomorrow and take a look

Nice to see the Viper getting some much awaited love

So best off taking AIM7s then?

Bumping to see if there is any new news on this from ED

Yea he's used the word symbol interchangeably 3 times for all symbols displayed in his example, I guess this could be confusing however there is enough information to be able to extrapolate the overall meaning.

Actually if you look at the compass rose it shows north is down to the left so this actually correct

The easy way to tell what the Hook is relative to is by looking at the arrow at the end of the hook line, this should help you orientate Something that helps me is to use "hookBull" so when you get a bulls eye calls from friendly AWACS you can get an estimate of where they might be in relation to your own jet. Its not accurate but it can help.

Holding DMS right long will also allow the TGP box to snap where ever you are looking

If you have the FSSB then use the FSSB axis and not the Warthog axis, Something I noticed recently was the constant jittering of the control surfaces when you are applying any pressure, the only thing I could put this down to is the Warthog board has far less resolution than the FSSB and causes weird behaviour. I did initially check for duplicate bindings but once i realise this was not the case and switched over things appeared to get really smooth

Something annoying is the cursor getting washed out as you try to change contrast and brightness settings, i thought the symbol brightness controlled the cross hair brightness and the TGP information around the outside. Messing with Symbol brightness seems to do nothing much at all.

I'm wondering with the DCS install size now approaching a rather large size would actually save some space if you start to include other objects that could also benefit from Taz's discovery. Seems to me that there are some fairly considerable gains to be had not only in performance but possibly in storage size? Not directly related but when I started digging around in the DCS install I noticed a fair few legacy hold overs from the very early DCS days, things like unused icons and old GUI interface art that should have really been cleaned out along time ago. I'm wondering if all this could really do with refresh and some old files being deleted and trimmed out. probably wouldn't save much but at least it would be a little less messy