TKhaos

Forums and the E-Shop are two different logins. Have you tried logging into the E-Shop account or just in here? ED shsould have records somewhere of your payments that can be traced using either payment methods or email address so might end up having to contact support.

Think motion blur has been causing some issues and advice was to disable it, doesn't effect me as I disable it anyway as I've never really liked motion blur

That's what I did with both Invulnerable and Dead, also changed my name down the bottom as I forgot to do it and was always called New Pilot I've seen a lot of people messing files up recently, I always use Notepad ++ as it automatically creates a backup of the original file, plus it's handy because everything is colour coded going through lua files.

Just downloaded that, thanks saved me a lot of time as well.

There is 6076ft in a nautical mile so 1.5nm is 9114ft (2777m) so should be able to land a Hornet there. I haven't got that map to try but I do a lot of F/A-18C flights in and out of Batumi which is a short runway at only 7500ft (2286m) so got an extra 500m on that. I have had a few times where I've touched down too late and had to take off again and go back round. I will have to do a video sometime, I land shorter than that but it's not exactly a normal landing, airbrakes go on and pull the front up, bit like a cobra until it's past stall speed then put the nose down hard and sort of glide in, although that can go wrong sometimes and face plant the runway

Just had a quick look, not flyable but they got the Su-24M Fencer as Ai on 4YA Training Mods, wonder if you could add it as a deployable weapon with Ai? https://drive.google.com/drive/folders/1i0E2pMEAyzqIKNgAnSnChp8UUObX39SD Found a mod now that males the 4YA planes flyable, not sure it will work though as it's 3 years old and probably using the FC3 stuff. https://github.com/necr0n/dcs-make-flyable

They use them on the Su-24 Fencer, been used in Syria and Ukraine, think the ones in use now are a modified version. Guessing as they have limited Su-24 Fencer's it will be used on newer aircraft. It was originally reported by NATO as an Su-19, people seemed to think it was a copy of the Tornado, not just the design it was almost sporting RAF colour schemes. Maybe other aircraft like Mig-23, not up to date on their loadouts. Just have to see what aircraft DCS produce that can carry it, wonder if any of the Ai aircraft can.

It was on the DCS side, they were displaying a massive red banner along the top of screen with 'Authorisation Issues' written in it, also there was posts from ED staff stating there was a problem they were working on. I copied and posted this in multiple places, guess I forgot here

That's all the aircraft that stopped working after Malwarebytes decided to remove 18 of my DLL files, I got exactly the same message. Soon as I put the files back and stopped Malwarebytes removing them everything went back to normal. Was a bit annoying as it started off with 4 files so was just the SU-27 and SU-33, added those 4 back played for a hour and next day came back to it removing the rest of the aircraft on this list. Malwarebytes has white listed all the files now, think McAfee has as well so shouldn't cause problems again.

If you use anything like Malwarebytes that's been removing 18 files and didn't add them to the whitelist until earlier today. Mine started off with the SU-27 and SU-33 not working, just got a messege about it being not authorised and I had 2d 23h 59m before they were disabled. Then later the following day it did the same with the F-15C and A-10A and got the same results. I put the files back and worked fine.

Check your AV hasn't quarantined any files, especially if you use Malwarebyes as that flagged 18 files as malicious, they have whitelisted them now so should add back fine if you do a repair and not get removed again. On mine I removed two files it claimed were malicious and the SU-27 and SU-33 stopped working and gave similar messages to what you have, not authorised and it would disabled them in 2d 23h 59m. As soon as I put the files back it was fine.

Used to have the Virtavia Hunter in FS2004 and FSX, had a few things by them, sure the Tornado I had was by them as well.

I'm not sure as I don't use that myself, only time I have set the heading was in Mission Editor, on one of the tabs you got a little circle where the waypoint stuff is I think and you can give specific headings. Other than that I'm not sure but hopefully someone will know.

Hopefully it does get sorted as I got around 11 VSN aircraft I really like flying. It's a little bit annoying this has happened, while I do have third party mods I still support ED by buying offcial products which aren't cheap, if you buy every addon it comes to about £2k for the sim. In the last few months alone I've purchased the Spitfire, Persian Gulf map, A-10C II upgrade, Supercarrier, F/A-18C, Flaming Cliffs 3, FC 2024, UH-1H Huey and few other bits so it's not like people are using a free sim and just using third party.

Its's not a bug or a feature, FC3 doesn't exist anymore and all FC3 folders have been removed and replaced with individual aircraft folders so any third party mod that points to FC3 files and directories no longer works. As stated in my post above cdpkobra (VSN) has said they are waiting for the next DCS patch before proceeding any further, it's pointless to fix something if it only gets broken again a few weeks later with a DCS patch. Once the next patch is released they can decide which direction they want to go in to restore the mods to how they used to be. CubanAce has said in another post that the SU-57 is being worked on and they are creating a standalone cockpit, so that should prevent this happening again.

If you go into 'Settings' and select 'Views' there is a new 'Air Boss' view setting key binding. Using that should put you into the Air Boss area and you can do things from there, quite a few YouTube videos showing how it all works. All your normal Supercarrier views are in the 'Views' category as well, first three on the list are Supercarrier, then further down you got Landing Signal Officer and Supercarrier view. Some people have had problems with key bindings after the updates so just check they are still all assigned.

Yeah could do that, it's what I did with my Corsair memory and that's been fine, most people have issues when they try overclocking so I'm always skeptical when people claim it doesn't work. Your memory is listed, just different timings the newer modules are faster. If you look on the G.Skill site, just make sure I've used your correct motherboard these are the 64GB kits for your board. If your going to bite the bullet and just buy 64GB anyway have a look at some of the other kits because there are several faster speeds you could go for, just need to untick 3200 and choose what you want. https://www.gskill.com/configurator?page=1&cls=1529635169&manufacturer=1524725352&chipset=1524723693&model=1532077071&adSearch2=Capacity§64GB (16GBx4),Tested_Speed§3200 MT/s,

Probably find that QVL list was updated before the 2507 bios release, it's off there official website, shame they don't add dates when it was updated, that's just a photo the download don't work need to go to the site. https://rog.asus.com/motherboards/rog-maximus/rog-maximus-x-formula-model/helpdesk_qvl/

They don't show up on the QVL list, well the new one but all these do: G.SKILL F4-3200C16Q-64GRK 64GB(16GB*4) 16-18-18-38 1.35V ● ● G.SKILL F4-3200C16Q-64GVK 64GB(16GB*4) 16-18-18-38 1.35V ● ● G.SKILL F4-3200C16Q-64GTZ 64GB(16GB*4) 16-18-18-38 1.35V ● ● G.SKILL F4-3200C16Q-64GTZKW 64GB(16GB*4) 16-18-18-38 1.35V ● ● G.SKILL F4-3200C16Q-64GTZKY 64GB(16GB*4) 16-18-18-38 1.35V ● ● G.SKILL F4-3200C16Q-64GTZKO 64GB(16GB*4) 16-18-18-38 1.35V ● ● G.SKILL F4-3200C16Q-64GTZSW 64GB(16GB*4) 16-18-18-38 1.35V ● ● G.SKILL F4-3200C16Q-64GTZSK 64GB(16GB*4) 16-18-18-38 1.35V ● ● G.SKILL F4-3200C15Q-64GVR 64GB(16GB*4) 15-15-15-35 1.35V ● ● G.SKILL F4-3200C15Q-64GVK 64GB(16GB*4) 15-15-15-35 1.35V ● ● G.SKILL F4-3200C15Q-64GTZ 64GB(16GB*4) 15-15-15-35 1.35V ● ● G.SKILL F4-3200C15Q-64GTZSW 64GB(16GB*4) 15-15-15-35 1.35V ● ● G.SKILL F4-3200C14Q-64GVR 64GB(16GB*4) 14-14-14-34 1.35V ● ● G.SKILL F4-3200C14Q-64GVK 64GB(16GB*4) 14-14-14-34 1.35V ● ● G.SKILL F4-3200C14Q-64GTZ 64GB(16GB*4) 14-14-14-34 1.35V ● ● G.SKILL F4-3200C14Q-64GTZSW 64GB(16GB*4) 14-14-14-34 1.35V ● ● G.SKILL F4-3200C16Q-64GVK 64GB(16GB*4) 16-18-18-38 1.35V ● ● G.SKILL F4-3200C14Q-64GVR 64GB(16GB*4) 14-14-14-34 1.35V ● ● G.SKILL F4-3200C14Q-64GTZR 64GB(16GB*4) 14-14-14-34 1.35V ● ● G.SKILL F4-3200C15Q-64GTZR 64GB(16GB*4) 15-15-15-35 1.35V ● ●

I was looking at there new QVL list. If you were going to mix and match least these have the same voltage and timings on both default 1.20v (2133MHZ) and the overclocked 1.35v (3200MHZ) using XMP, not as pretty as the Trident but could tell people it's a feature G.SKILL F4-3200C15D-32GRK 32GB(16GB*2) 15-15-15-35 1.35V G.SKILL F4-3200C15D-32GTZ 32GB(16GB*2) 15-15-15-35 1.35V G.SKILL F4-3200C15D-32GVK 32GB(16GB*2) 15-15-15-35 1.35V G.SKILL F4-3200C15D-32GVR 32GB(16GB*2) 15-15-15-35 1.35V If it was me personally I would just go for what you suggested and get 4x16GB matched, I look at it like memory isn't something you upgrade every other month so better looking at long term value. Good it's sorted, bios updates can be stressful as you can brick the motherboard but least it's done now. I do tell anyone I do it for the risks that can be involved

It's been addressed in numerous posts by myself and others that the workaround is flawed and while it gives you access to fly the aircraft there are some major problems. The landing gear and flaps do not work off HOTAS or keyboard, so you are stuck with the flaps and landing gear jammed down. A majority of the time the trigger doesn't work, sometimes the launch weapon doesn't work and people are now reporting that some of the instruments fail to work. That is using both the the workaround method you describe and the hot fix by cdpkobra that changes the F-15C cockpit to the SU-25 cockpit. The authors of the mods have confirmed they are not working and will be waiting for the next patch before deciding how to proceed. One new thing I have had testing both workarounds is I will be flying along in a straight line and it suddently banks left, goes into a steep circular dive and just crashes into the ground, all control of the aircraft is lost.