mkiii

It does seem better in 2.5. However, I did notice that there was a tendency for the sensor to lock onto the poles of streetlamps (not the lights themselves), instead of vehicles moving down the road behind them. I'm not sure that the steel poles would provide a better target than the vehicle behind. Perhaps this should be corrected, it seems that those poles are a little too hot.

I get flashing on 2 monitors to the side of the main monitor (when black & unused in 3d) that seems to correspond to tracer fire if for example, I attack a tank. With the labels bug currently affecting multiscreen setups, I also see labels flash by when they are turned on. My 4th monitor designated as a viewport for MFDs etc doesn't get the flashing.

Multiscreen or Single? Kadins fix changes the appearance of the labels, but (I assume) not where they appear if affected by the ongoing and recurring multiscreen label offset bug, which makes them appear offset to the right by a monitors width.

Yep. This is the same as we had in 2 then 1.5, and now 2.5 Which is odd, because I'm pretty sure it was fixed a while ago. The old fixes where you either set the GUI to the leftmost monitor or allow it to spread across all screens doesn't seem to work now, not that they were satisfactory anyway.

It's not the only ship like this in 2.5 The ones I have found are the Ivanov, Yakushev and Zwedny A minor Texture issue also on the US WWII Attack ship Samuel Chase flags. they are one sided.

Not the command prompt. Create a shortcut to DCS_updater, Right click & open up it's properties & add the --apply repair bit to the end of the command line in the "Target" section of the Shortcut Tab. Then run. This will force the updater to do a repair & if sucessful, it should replace any missing files. EDIT: Since you are already updating.... it may be too late, but you probably aught to get familiar with the way this works once you get up & running, it will save you a lot of frustration. To make life easier, you can grab a copy of the Excellent DCS Updater GUI Utility by SkateZilla. https://forums.eagle.ru/showthread.php?t=160053

Confirmed here. The explosions in 2.5 look pretty good to me in DS. Without it, apart from everything looking washed out, the explosion effects are minimal. A fizzle of sparks, and a puff of smoke. It may be just me, or are the blast effects greater than before. Trying the A10C Quickstart Spring Easy mission, I can take out both trucks and the soldiers on the second target with one Mav. Before, I always had to do a re-run with guns to hunt down the troops. Maybe I just got lucky ;)

Haven't checked the WWII Assets, but I haven't got a problem with the Spit Trigger / Button functions. These remain as I had them set up before and work as expected. I did have a slight problem initially, in that NONE of my WH controls were visible or usable in DCS. I ran the Thrustmaster Target Script Editor, Device Analyser and tested that all was OK and restarted DCS and they were now there and using my previous assignments.

Your Monitor & GFX card settings might also be contributing to the effect, so there is no one in-game setting that will suit everyone. For example on NVIDIA cards, Adjust Desktop Colour Settings can be set to allow "Other Applications" to control these, in this case DCS, or be set to use NVIDIA settings. So it might be worth checking that before tweaking too much in DCS.

Did you already have a copy of 1.5 or 2.2 installed? That saves a lot of time because a ton of files are copied from the old install rather than downloading. Right now though it sounds like you at least have enough to get it running, so perhaps it might be better to run your DCS_Updater from the bin folder with the following command line :- C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe" --apply repair That (AFAIK) should just look for missing / bad files, and download them.

Mine was very washed out initially with DS, so I set Gamma to 1.6 to correct it, but after a few false starts, a reboot and a reset of options lua, it now looks ok on 2.2 with DS ON, and if anything is a little too dark and contrasty. I have found that setting it up to look OK on one session might not mean that it looks good the next time. presumably this is something to do with the shader cache?

I agree that the various maps do not appear to be consistant, but I have only really been experimenting with instant action missions so far, and the time of day & season on those does vary a lot, leading to some noticable differences. However, some small setting changes seem to have a large impact. I have also noticed that my gamma settings seem to be a bit variable. It defaults to 2.2, which at first was completely washed out, so I set it to 1.6, which was good. Then I had to delete options.lua and gamma was back to default 2.2, but was now OK. Odd. I'm getting the feeling that perhaps the shader cache might have something to do with it. We were advised that it might be necessary to delete the cache folders after all, but doing that after each tweak is going to take quite some time. All that being said, I'm very pleased that this version seems to run at a decent framerate, even with settings pretty much maxed out on my trusty old GTX 970, and various shader/gfx problems tend to work themselves out as people become more familiar with the settings and report what they are using to fix things. It is still in beta after all.

What is your gamma setting when on DS? The default seems to be set up for some freaky Apple MAc Monitor setup, not my steam powered PC, but at least that is easy to test. I'm also seeing the map problem in the A-10C. Have you noticed strange artifacts when viewing the exterior, like a very high frequency noise texture, that seems to consist of tiny swirl patterns when you zoom right in? It also seems to appear on the HUD lenses (& projector part of gunsights) as a strange dark speckly shadow. I'm still experimenting, but it does seem that you really need to restart after tweaking any of this stuff, which can make testing a bit time consuming.

Happened to me. A reboot fixed it. I assume your original post didn't mean you were running 2.5 then trying to start 1.5 as well, because that will (I assume) produce the error legitimately. If you haven't already done so, you might also want to try starting settings from scratch by deleting your existing options.lua from Saved Games.

Same here. I'm getting better (about 20 -30) FPS on slightly higher settings than before. Very happy ;) Initially though, had a few GFX glitches, but following the advice to turn off MSAA and set Gamma to about 1.6 all is well. Caucuses v nice.

Probably best to not just put "Delete", just add a post stating your current understanding, otherwise no one who didn't see your original post can't possibly gain anything from the thread.

The RAF GR7/GR9 could also carry a centreline Recon pod, which is cigar shaped like a tank. I think the USMC AV8B also has a similar pod.

The commands are hard coded in mods\aircraft\AV8BNA\joystick\F16 MFD 1.lua and F16 MFD 2.lua. If you want to assign other commands to them, then you need to add a link in the files to the keys commands. To do this, modify the top of each lua to read like this:- return { local res = external_profile("Mods/Aircraft/AV8BNA/Input/AV8BNA/Keyboard/default.lua") forceFeedback = { }, keyCommands = { ........

Who wouldn't want a rotating bomb bay eh? Bucc gets my vote. Lets see how the chaff n flare monkeys manage with a one shot cardboard box taped to the inside of the air brake to dispense the one (count em) shot of chaff.

I originally modded the FM\FMOptions.lua file for the spit to alter the friction of the tail wheel castor via this tailGearAxleFricM0f = 35.0 -- Original 11.0 ...amongst other things.. which improved it for me at least. Also these, the top one making it less like a power ball bounce:- tailGearSpringForceFactor = 11000000 .-- Original 17000000 tailGearStaticForce = 6000 -- Original 3000

If what we had looked like the A-10 vid above, which is in harsh sunshine, then it would be great. Look how fine thos crackles are. They are about 50 times finer than what we currently have. The dings (probably on the inside of the canopy, caused by pilots helmets hitting the perspex) are something that we are missing too. In Xplane, that sort of thing is used to give you visual references when using head tracking. EG. There is a small ding in the windscreen of the Cessna that "just happens" to be where your line of sight for the horizon falls. There is usually a separate "dirt map" that deals with that sort of thing though, and it is separate to the crazing effect. At the moment, this is dealt with by a small 256x256 normal map that is tiled all over. You can just delete it as a temporary fix, and the effect will be gone. Or if you have the means, edit it or create a higher fidelity version. Look for \DCS World\Mods\aircraft\AV8BNA\Textures\AV8BNA-CPTAV8_RS_10C_BUMP.dds & delete/hide the file.

Agreed with DaveRinder. Have done some FLIR stuff for RL Sim, and it's a world of pain to get right. Basically, you not only have to identify the materials of everything in every part of the terrain & each object, you have to also have to tag how that interacts, how it cools or warms, what it's current state is, how the ambient temp is affecting it, and a whole bunch of other factors that essentially mean a ton of work that can become a mess on screen. Far better to just fake something like ARMA & have a chance to see targets in the first place, in a way that doesn't overcomplicate matters.

I'D LIKE TO COMPLAIN ABOUT THE PEOPLE COMPLAINIING ABOUT PEOPLE WHO COMPLAIN THAT OTHERS ARE COMPLAINING. At least I think I do. Now I'm not so sure. And my birthday is in March too. ;)

If any aircraft I had worked on in the past had crazing like that, it would be grounded. Scratches & dinks, and some micro crazing yes, but not 3mm wide cracks all over the windscreen & canopy. You can edit the normal map that is used for this (and just about everything else) to tone it down or remove it completely, but it's far better to have the default setting look right. The bitmap used is tiled to create the effect, so maybe it's just that the tiling is not fine enough, or maybe it just needs to be higher res, with finer lines.

I use the paddle switch for intermittent braking, using the W command, "Wheel Brakes" as in the real thing, but also use the TMS Up and Down buttons to control "Wheel Brakes Increase" & "Wheel Brakes Decrease", to allow me to set the position of the brake lever to any position for either full parking brake or just a little. A quick touch of the brake lever releases the brakes from this setting immediately. It works quite well imo.