Lange_666

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.

- Removed everything concerning Scratchpad i had installed. - Fresh download of latest Scratchpad - Fresh download of latest Scratchpadplus - Compared both with previous download, they are the same. - Installed it again, folders just look like your now (except in Hooks folder i also have DCS-SRS and TacView in there (previously also)), enabled keyboard and sitrep - Scratchpad works but no keyboard, no sitrep..(and no clear button either when i add that). , just the main scratchpad with a working F-10 map thing. - Stuff that works works both in 2D and VR. Could Windows version have anything to do with it? I'm on Win 10 Pro, latest version.

Went through the entire topic again. Mmm, looks like the older versions worked without the extensions, the keyboard was build into scratchpad-hook.lua (if i'm correct). I can get this version to work, with a keyboard that works but in that version the F-10 coördinates thingy doesn't work. If i switch to the latest version, the F-10 stuff works just fine, but no keyboard, nor anything of the stuff in the Extensions dir works. This might be due to the fact that the Extensions dir sits in the wrong place or that i put the files that are in the Disabled dir into the wrong place to make it all work, but then i tried all places i could think off... no joy on any of the extensions. Can someone for who this entire extension thing works (including keyboard) post a few saved games directory screenshots so i can compare?

Weird that it doesn't work anymore (keyboard showing that is or any of the other extensions). Scratchpad itself works, also pulling coördinates from the F-10 map works. I just miss the keyboard. This is on a 2-weeks old install, no mods. On my previous DCS install (which lasted several years), scratchpad worked and when i installed the keyboard, it also worked from the first time. So it baffles me a bit why it doesn't do now.

Same here, no keyboard anymore Used to work fine, i'm on a new install (new PC), installed latest version of the scratchpad and added the keyboard but it will not show up. And without keyboard, the scratchpad is pointless in VR. Must say that the other extensions (clear, sitrep etc...) don't work either when moved out of the disabled directory so i guess they need to be copied into another location... although i tried about every location already.

Just gave it a go, works fine right here on 2.8, just as it did in 2.7.x Didn't need to change anything, all bindings from 2.7.x where still there.

After the update to 2.8.xxx i took the F-18 out for a little test flight on the Marianas. This runway texture problem is still there on every intersection. The screenshot below is from Antonio B Won Pat airport.

LOL, payed 475€ 3 weeks ago, local shop had them at 519€ (currently 369).

Update: Changed the airflow from the top picture to the 2nd one (but left the second exhaust fan on top). Will add a 3th fan on the front as extra intake (below the radiator, but only have room for max 100mm fan) to equal the balance between intake and exhaust. Together with this change i also changed the thermal pads on the GPU. Used Gelid pads for memory and the other stuff and Thermal Grizzly Kryonaut on the GPU (stepped away from liquid metal after seeing the GPU). Gave -6°C on the GPU, -8°C on the hot spot and -11°C on the memory so not to bad. Had expected a little bit more but it's not that easy to define what the exact height of each pad needs to be and because i found 3 different measurements on the tube for my GPU card which made it hard to decide which one was exactly the right one.

The top ones are filtered, the one on the back not (but it's not dusty in here, i'm a clean boy). Another question then: ventilators in front of the radiator pushing cold air through the radiator to the inside or vents at the back of the radiator pulling cold air through the radiator to the inside? And why... Another reason why i choose setup one is that in setup 2 hot air from the radiator flows over the GPU which already gets hot on full load.

New PC, Case: Be Quiet Pure Base 500DX. AIO Cooler: 280mm (2x140). Problem: Overlooked the fact (which is in the specs) that a 280mm AIO cooler can't be mounted on the top (fixation holes do exist) due to the motherboards northbridge cool element being to thick. Radiator alone or fans alone is no problem but together it's a no go. So decided to mount the AIO on the front, radiator on the inside, fans on the outside pulling air from the case through the radiator to the outside. So far so good. Mounted two 140mm fans on top and one 140mm on the back to draw air in but something is keeping me awake that that's not the best solution. So i currently have this (not my setup, just an example): Instead of 1 i have 2 fans on top and my radiator is mounted so that the waterconnections are on the bottom (that way the overall airflow is less interrupted). However, it's called an unusual setup but OK. The most common seems to be the reverse of the one above (not my setup either, just an example): So the opposite airflow of what i have. Why did i choose for the first setup? If the cooler is mounted on top then mostly hot air in the case is drawn or pushed through the radiator to the outside. In the first setup that idea still stands, on the second one the radiator should stay a bit cooler but hot air from the radiator is drawn into the case which i don't find ideal. What do you people think?

I have set them up on the MIC switch (Thrustmaster Warthog, script), for every heli and airplane the same, only depending on how much radio's the heli/airplane has (same goes for other functions). Big advantage at my age: only have to remember it once. PS: i don't care about mimicing real controls, for that you need a full copy of the cockpit.