Lange_666

Not in my collection: - Mi-24P Hind - Gazelle (trialed it....) - Mi-8MTV2 - FW-190A8 - Mosquito - Yak-52 - I-16 - JF17 - Christen Eagle (no idea what this is doing in DCS) - MIG-19P - Mirage F1 - NS430 (but then this isn't an aircraft isn't it?) - Most campaigns I own: i play - FC3: - A-10A: Yes - F-15: No - Mig-29: No - Su-25: No - Su-27: No - Su-33: Trial landings on the Kuznetsov - Combined Arms: No -Jets: - A-10C (and II): Yes - ASJ37 Viggen: No - AV8BNA: No - C-101CC/EB: No - F-5E-3: Yes - F-14: No - F-16C: Yes - F-18C: Yes - F-86F: Yes - Hawk: Yes (but is no more so No actually) - L-39: No - M-2000C: No - MIG-15Bis: No - MIG-21Bis: No - S-25T: No WW2: - FW-190D9: No - Bf-109K-4: No - Spitfire: No - P-47D: No - P-51D: No - TP-51: no Helo's: - UH-1H: Yes - KA-50: No (first bought as stand alone, played it suite a bit back then) - AH-64D: No (did quite some time in it in the beginning but the constant switch between front and back seat to get things done is not my cup of tea) Mods - A4: No (not installed currently) Terrains: - Caucasus: Yes: offline/online - NTTR: Yes: offline - Persian Gulf: Yes: online - Syria: Yes: online - Normandy + WWII Assets pack: No (still have to see one of those assets, lol) - Channel Map: No - Marianas: No (but since my system upgrade i'll eyeball this one now and then) - South Atlantic: No, not yet (far from finished)

If you have room to put 2 versions side by side, you can always make a copy of your stable version and update that copy to latest beta. You can then switch between the two. If the beta is messed up (happens now and then) you can always fall back to that stable version without the introduced bugs. Use SkateZilla's updater for the beta transistion from your 2nd copy:

AM4 X570(S) motherboards could have USB disconnect problems. Should have ben solved with a BIOS update but on mine i still had problems. I had one with MSFS where my Warthog would disconnect briefly while loading the sim (always on +/- the same loading point). 50% of the time it would disconnect briefly and show a message in the Target Script Editor that the running script was interrupted by a disconnect. First thought it was the script but an empty one gave the same problem. Second thought was MSFS (did not have/see disconnects on DCS/IL-2) because when i deleted the Warthog Combined profile in MSFS, the problem was gone but as it turned out only temporary. 3th was updated chipset drivers, didn't solve the problem either. I then stumbled on a USB disconnect problem with AM4 X570(S) motherboards for which 2 workarounds where mentioned: - Change the C-state of the CPU in the BIOS: didn't work - Add in a PCI USB expansion card which did the trick, no more disconnects. Then i bought a USB-C to USB-A Y cable and connected both Throttle and Stick on that cable and used the USB-C port and removed the PCI expansion card: no more disconnects.

Has the overall light intensity in the room changed? A reset of Guardian should help (even if you only set a floor level).

@Steel Jaw: There is indeed an argument to many to be correct but your code should compile fine (it does here, compiler doesn't take that second argument into account if it's a 0) so this line isn't the problem. Look at a line before or after (if you have the arguments on separate lines it could be a few lines up or down. Post a bit more of the script pls... PS: Didn't i tell you before to add spaces in between the arguments to increase readability and error solving? You lazy bastard you...

LOL, wasn't even aware that it existed in 2D (after all these years). For me it's only needed in VR because if you have a 2nd monitor and the mirror is full screen on the 1st monitor, you can't by accident click on the 2nd one and loose control. On the other hand, if you quickly need to do something outside VR on the 2nd monitor, you're stuck on the 1st one. In 2D with 2 monitors it's a non-issue for me since i mostly have some other stuff running on the 2nd monitor anyway (perhaps that's why i never noticed it existed).

Still have my Warthog but the sticks base has been replaced with a Virpil WarBRD. Compared to this the Warthog stick base is just not on the same level as the Virpil. Used to have a TM Cougar before with an Uber modded stick gimbal and when changing to the Warthog, the default gimbal just didn't cut it, it's almost trash compared to a decent "smooth" gimbal, either modded, VKB or Virpil. So i confirm what rob10 says here above, same goes for his comment on the rudder pedals, went down the same road: CH Pro pedals to MFG Crosswind (although i don't use the original footrests anymore).

Coming from: i7 4770K @ 4.5 (instead of 3.5), 32GB 2400 DDR3 and a GTX 1080Ti 11GB New system: AMD 5800X3D, 64GB 3600 DDR4 and a RTX 3080Ti 12 GB Over time, i had to lower settings step by step on my previous system to keep an overhead so i could run a fixed 60 FPS cap. On more demanding maps (Syria, Marianas, South Atlantic) this became an issue, same for online play with a lot of players or units and when the MFD's came into play. On the new system, no such thing, cranked up the settings again to high (not everything because i don't see the difference between some settings anyway) and the overhead over 60 FPS became much bigger, depending on the situation of course. I don't chase numbers but one test i did was F-18 Caucasus free-flight, old system, settings on high to medium, 2560x1440 res: FPS +/- 80 to 90 New system, same settings 170 - 180 FPS (fixed cap inside the config file, didn't bother to remove this to see max FPS i could reach). One thing i regret is the 12GB VRAM, on higher quality maps this is easily filled to max, same goes for when running VR.

That option resides under the VR tab in the settings which means it should only comes into play when you are in Virtual Reality mode.

@speed-of-heat: did you run a 2D test also?

It all depends on who is online. You can get an overview on what's currently happening on the Gadget: operation:BLUE FLAG (buddyspike.net) You can go in solo when nobody is online and just do your thing that you think is right to advance the battle for the side you're playing for (you can only switch sides when the battle is entirely over (or by demand directly on their discord channel). You can go in with a bunch of people on your side but with nobody willing to (or being able to) coördinate stuff or... You can join on a moment you know that there is a commander (or more then one) online who is overseeing the battlefield and gives tasks or fill you in on the current state of progress so you (and your buddy's) can make a decision on what to do next. It's always different and when even only one player is playing on the opposite side, you always have to count him/her into the equation when you set up a mission or contribute to a given task. Also, after the server is restarted (every five hours), you can download the Tacview file from that past five hours and see how the battle has progressed over those five hours. You can pick out any player that has logged on during that time and also watch every AI unit that has moved or played a part.

Pick an online PVP-PVE server like operation:BLUE FLAG (buddyspike.net) It offers fixed scenario's but within an online community so every time you log on, the battle between red and blue has progressed up until a point where either red or blue take the entire map. This can last a couple of days to more then a few weeks for each scenario. You can dogfight, bomb, fly logistics and, if you have the Combat Arms module, play with ground units. In a commander role you can launch AI air and ground attacks, launch and set up drones, tankers and AWACS, move the carrier group, etc... Mostly there are 3 scenario's running on various maps and various time settings, currently Persian Gulf - Modern, Caucasus 60's Cold War and Syria 80's.

I'm on the latest (and those before that) and i ain't seeing that. No increased idle power draw and certainly no 100% utilization at desktop. Hearsay (or better readsay)?

A better CPU will not prevent this. I have the same, one nice example is Instant Action F-16C Take-Off Caucasus. If i take-off, continue flying to the end of the runway and then turn right, stay low and then when i'm over the tree line then there is always a short stutter. Always. I had exactly the same stutter with i7 4770K + GTX780 3GB with 16GB RAM, then later with a 1080Ti 11GB, then again with 32GB RAM instead of the 16GB and again with a 3080Ti 12GB. I now have an AMD 5800X3D that replaced the i7 4770K, have 64GB RAM and FPS capped at 60 or not capped 120+, still the same stutter at exactly the same place.

Same here (no mods), standard cloud settings in VR give a lot of stripes, certainly at the edges. It's better on high or ultra setting but they looked a lot better on standard in 2.7

I just wonder why the performance of the 4090 goes below that of the 3090Ti between 2:20 and 2:35 in the above video.

I looked at the wrong profile, VRDirectX instead of DCS.

I have the latest drivers (526.47 currently) and on a fresh Win10 Pro install with the latest updates, these values seem standard now...? Can't be any old profile i was using because everything is installed from scratch due to entirely new PC.

Correct!

I tried that one but with the keyboard file that doesn't work so i thought that that version didn't work. Now i know that the problem was the keyboard file for that version. The non extension version (0.61) does not work with any keyboard file. Personal opinion: The different versions and options (made by various people) make it messy if you get stuff mixed up.

@imacken: Found the difference already, the hook file you use contains an extension part in the code, the 0.61 version from Github doesn't (just did another download to be sure). Hence the difference in filesize, yours 28KB, 0.61 is only 20KB. There are more differences then just the extension part but that one is the major difference. I'm gonna use the one you currently use.

Thanks for that, just tried without the config file, your version works including Keyboard (changed it already to an azerty layout), CLR (not needed since it's included in the keyboard) and sitrep. Didn't use the config file since it worked without. Now... why does your version work and the latest 0.61 doesn't show keyboard, clr and sitrep?. One thing i already know is that the keyboard file i used doesn't work on your version either. But that's not all because now also SitRep and CLR works so the problem lies somewhere else. I'm gonna check the hook.lua and window.dlg against each other because they (version 0.61) differ in size then yours.

Played around with different versions and a combination of those. Latest version 0.61: - Works including the F-10 map but nothing of the stuff in the Extensions folder show up, no matter where i put these, so no keyboard, no sitrep, no clear. Version 0.50 (Github): - Works with working keyboard (integrated into scratchpad-hook / scratchpadwindow). Version ilfy53e (from somewhere in this topic): - Works with working keyboard (integrated into scratchpad-hook / scratchpadwindow). Files (both hook.lua and window.dlg) are all of different sizes in each version and when compared there are quite a bit of differences in each. Then i ran combinations of the 3, either the hook or the window file but then nothing works, no scratchpad at all. Then i ran scratchpadplus solo (removed everything else) because it also contains the same files, hook and others, no scratchpad at all. @imacken: could zip up your currently hooks and scripts folder and include the scratchpadconfig.lua from inside the Config folder and PM me this? I'm just curious if there are any differences with what i have, what makes the extensions works on your version and not on mine?

Dates and times don't matter, they show the install date, not the file date. But... I have 20 KB as size for the scratchpad-hook.lua instead of your 28 KB (scratchpadplus.lua is the same). That is weird because mine is from the latest version, freshly downloaded 3 hours ago. Also, i'm curious about the size of your CrosshairWindow.dlg and ScratchpadWindow.dlg because i have 3 versions (2 older and the the new one) and they all differ in size. Currently CrosshairWindow.dlg is 2 KB and ScratchpadWindow.dlg 8 KB (version 0.61) but those in Scratchpadplus are 2 and 9 respectively.