Leg2ion

Apologies @Flappie, so if I add in a custom lua to replace the stock one as per my attached which includes not only the stock squadrons but all other UK Aviation squadrons - the logbook still only shows the basic squadrons in the logbook that your image shows. If I edit the basic lua you have shown, and say change 'troop' in one of the lines to 'squadron' - that squadron still displays in the logbook - even though the command line is incorrect - so is pulling in the squadrons from somewhere other than that lua? If i drop a different png into the 'MissionEditor\data\images\Countries\UK\Troops' location but named the same - so basically say replace the 11sq png with a different image but keep it named 11sq - the new image is reflected in the logbook - so that relationship appears correct - but the logbook for whatever reason isn't pulling in the additional squadrons. UK.lua

Is the custom livery system 'broken'. Have been using a UK skin for the AAC AH, and noticed yesterday that the AAC eagle and Tactical flash have what looks like the 101st Airborne superimposed over the top?

Just to expand this a bit - this is not just on the A10/USA - also have issues with other countries. In my UK folder I have all UK Army, RN and RAF squadrons (courtesy of @dreamingbadger - Additional UK Squadrons for Logbook) and same issue persists. So the lua file details all the squadrons in the correct format, but logbook only details the basic RAF squadrons. Thing is - if I edit the original lua and make some cosmetic changes to the spelling the logbook still picks up the original basic squadrons - so where are they being pulled in from? It still links to the png images though - and if I change a squadron badge (but name it as an existing sqn) this pulls through and is displayed.

Hi @Boomer25wa - did you get anywhere with this. Just noticed the same - my custom squadrons and patches are still in their respective folders - but not being picked up by the logbook? Thanks in advance.

Hi @MAXsenna thanks and good steer - found it in Norton quarantine (no bloody notifications from Norton though) - stating it is infected with an IDP generic virus? My last update was the latest drop on Xmas eve. Oddly it had locked my standard bin from having any files dropped into it as 1st thing I though was to simply copy across, but now I have restored the original I can copy files into it no problems. I am thinking latest Norton update may have caused some issues as have also been getting repeated warnings about Elite dangerous accessing my webcam... Anyhoo - all done. Thanks.

Hi All, Did a quick search but cannot see anything the same. Flew a mission Sunday night - all good. Went to start DCS last night - and got the below. Appears my DCS.Exe in my standard bin folder has disappeared. Appears there is a DCS.exe in the bin-mt folder, but without an updater launching through to it. So I can either run the updater which doesn't launch DCS, or the .exe in the MT bin with no way of updating? Any ideas/assistance would be of help? Thanks in advance.

Hi @GAJ52. Think there are a few of us the same - my main ride (though still learning) is the A10C, though learnt this after the Blackshark - which I have for the most part now forgotten how to fly/fight (took it up the other day and it was a disaster!) Agree with @rcjonessnp175 - slowly does it. The training missions bundled with the AH are OK as well, and get you used to taxi, hover, hover taxi and into fwd flight before starting on the weapons. I can now take off, land, hover (for the most part where I want and not where it wants!) and have just started weapons school - after an age - but its worth it - though with the odd dip back into the A10 to keep current (and just blow stuff up!)

Go with @Yurgons response. There are a few posts detailing the same issue. And yes - you have the workaround - just nudge the throttle levers forward slightly, once you are up and running and then starting to taxi you shouldn't get any repeat issues...

Yep - same here. Was OK yesterday 24/07,, but today - nope?

And catapulted straight back to that cold war era - details of 'surprise and shock'. Even the force summaries is frightening when you look at the figures - interesting reading.

As per @MiGCap1 - take your time - get it right. In the scheme of things with so many recent additions - what is a few weeks? Your efforts very much appreciated.

This is a really good guide which should assist: Failing that - what are your 2 monitors resolution - assuming monitor 1 on the left and monitor 2 on the right and are they aligned with each other as per step 1?

Ok - set up a mission out of another runway - no problems whatsoever. Then did the same out of Sochi - the MFD blanking re-occurred. Looking at the MFD there appears to be some type of tile mismatch on the MFD - almost as if different data sets have been used? So, and never having used them before, installed Flappies raster charts/maps for the region (and oh my god they are awesome!!). Minor blanking still occurred - not as severe though - but definitely still there - just slightly further out to sea. Just ran the same 'mission' in A10 - no problems -so guessing AH/Map/Location related? MFD6.trk MFD5.trk

Hi @Floyd1212 - yep (and many thanks for the input - all suggestions appreciated) - emphasis on 'had' followed by slow repair with no improvement - so thus far have: Noticed issue. Reported. Removed Texture packs - no change. Slow Repaired - no change. Swapped to 'basic' 1 screen setup, no helios (viewports patched, viewports patching removed) no head tracking - no change. Included in this is no viewport exports at all - so no other screens involved. Moved back from DLAA to MSAA - no change. I am not using reshade - but if I recall the screenshots were with the CGTC pack installed so maybe that's why things appear different - re-installed after previously removing them with no change. My gamma - I think - set as 1.8. Used both the basic DCS launcher and the MT Launcher (though not sure if that makes any difference nowadays) - no change.

Hi @Lord Vader. So - binned off head tracking, helios and dropped to single screen (1920x1080) using the '1 Screen' profile available in settings. Flew the same - same results. Then, had another thought and uninstalled all the helios patches - just in case. Restarted DCS, same results. So - screenshots with/without blanking. Two tracks - #3 before removing Helios patches, #4 afterwards, and 2 x logs - 'dcs' for MFD3 and 'dcs2' for MFD4. One thing to note - and not sure if you can pick it up in the tracks - but the MFD screens did appear to jump in terms of video realtime. MFD3.trk dcs.log MFD4.trk dcs2.log

Ah - apologies. Different mission. Will have a play and see if I can replicate the issue and reply.

Also had an issue whereby I started in a HAS/Shelter - and dependent on my view was getting intermittent shadows/sunlight when I looked down out of the cockpit. Obviously I didn't save the track - but will see if I can replicate it in due course - unless of course that is a known as well?

Cheers @Flappie. I did say 'around'... Definitely not weapon related though? I guess the question is which version is correct - the lighter/brighter version or the more colourful darker version?

Sure I read elsewhere that this was linked to carrying certain weapons (though now cannot find that particular post) - and seeing as I have no weapons/power...?

Posted this here as unsure whether an overall 2.9 bug or related to the A10C2 (or Nevada for that matter)? Have seen a similar post where I believe it had been declared as resolved - possibly linked to the weapons being carried? I created a mission whereby my A10 was sat on the tarmac with no power no weapons in Nevada - purely so I could get some screen grabs of various instruments for Helios. Didn't pay much attention to things as I was zoomed in and trying to align my view squarely with the instruments, but there appeared to be a dimming overall around a minute after starting. So, went back into the mission, external view and zoomed out. Around 50 seconds in - bang - everything goes a little darker. Not sure whether it returns to normal as ran out of time - but have attached some screen shots (bottom one at mission start and upper after the dimming) and the trackfile. Dimming2.trk

Had a look through the various forums - but couldn't find anything on this. Set up a training mission in Caucasus - headed out towards the coast, and the sea intermittently blanks on the moving map during flight. All cockpit settings left on default from a hot start. I don't think this is the same issue reported for Kola where the map completely disappears due to scaling - it is almost like the sea has been cropped/photo-edited out using a lasso on an intermittent basis - and drops in and out. Only mods I had running was Taz tree mod and CGTC Caucasus Texture Pack. Screenshots and trackfile attached - along with a log file. Have just carried out a full (slow repair) - with no improvement. dcs.log MFD Blanking.trk

Mine defaulted to other payment (card or GPay I think) - so came out of the transaction, and then had the option to select paypal.

Hi @Morpheus - many thanks for that. Cracked it!

Yep - did that hence the ask. The two folders (circled) are not in my vfstextures folder.

Hi @Taz1004. Just looking at your tree mods - and noticed in the downloads there are two 'normal' uncompressed folders (Noisewinter and Noisewinter.min). What are these for - as cannot find similar folders in the DCS textures folders?