Worrazen

Yeah I saw it ... really busy so I didn't comment yet, I'm basically speechless because there's really good details explained such as resupply/rearm relationship with cargo trucks, many many things that will be so wonderful for new people. The tutorial sections could point the people to the manual first, maybe there's a sticky about it already, should be a button somewhere in the main menu too (unless I missed it)

1. Download the Microsoft ADK for Win10 - https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install The current latest is 1903, direct link: https://go.microsoft.com/fwlink/?linkid=2086042 2. Use custom installation and you only need to install the Windows Performance Toolkit (WPT) so only select that, this is a web installer, it will only download the selected components. (there is offline available but for the whole ADK) 3. Download and Install the NET Framework 4.8 Runtime (not developer pack), the WPT GUI may need it (i'm not sure which ver, but get the latest and you're safe) https://dotnet.microsoft.com/download/dotnet-framework/net48 4. Reboot 5. Search for "Windows Performance Recorder" and start it, expand the tree and deselect everything else, only select the checkboxes for CPU Usage, Disk IO, GPU Activity. And make sure you don't use Verbose detail level, switch to Light. Verbose is default and it will never remember the setting. 6. Start DCS, load your mission fully, where you know it's laggy (not a big mission tho) but do not start playing yet so don't unpause. 7. Start the Recorder, then go immediately inside DCS and play. Do not change the views or rotate the camera when recording, keep it strictly stationary at all times. Record for about 1 minute. Make sure the issue is actually present when recording, or else you have to scrap and cancel and repeat the recording. Please SAVE the file immediately, a new dialog will appear asking to confirm filename, click SAVE at the bottom immediatley, waiting there AFAIK creates an annoying section of uselessness (IMO) in the graph called "trace rundown", rename the file if you wish later manually with the explorer (such as DCS_version_description_Date). Do a test recording before, to set up the output path, it should remember it, while filenames are auto generated. 8. Do several recordings of variable lenght from 30 seconds to 1-2 minutes in various sections of your mission. Don't record over 2 minutes in one piece. Do not select a mission with too much activity, not too many AIs, prefer small mission. 9. The output is saved to .ETL files in Documents or wherever you saved it, make sure you at least zip them to compress the size significantly, use WinRAR or similar to use much better compression than the old ZIP format uses. Upload them here so I can take a look, you can do it yourself but I think you already got full hands with this especially if you're doing it first time. You can't really take a look at it quickly, it would take you hours to do anything (in depth stuff takes days, weeks) to get the experience to use the analyzer correctly, and to know what to look for. 4-5 recordings should well be enough if the spike is happening all the time, across all modules, missions, etc.

Hyperloop wasn't his idea anyway, a vacuum tube train system is a no brainer, I watched documentaries about it on Discovery Channel in something like 2004. Elon Musk is a total fraud anyway, stealing the Tesla name, saying one thing and doing another, but mostly a front man for a variety of very rich interests and future-obsessed stockholders who actually run the whole show, those are incredibly obsessed with AI controlling everything, space and going to mars. Then go to mars and leave us alone. The fanboys of Elon Musk don't understand it's all private, it has no meaning for humanity, everything they do will be for their benefit, if they capture comets for mineral mining, it's their property, if they land on mars, it becomes their private property. https://www.zerohedge.com/technology/tesla-gets-approval-continue-cutting-down-thousands-trees-build-its-german-gigafactory https://www.zerohedge.com/energy/ntsb-blames-tesla-and-us-regulators-fatal-2018-autopilot-crash https://www.rt.com/business/482188-elon-musk-cobalt-crisis/ Skip to 8:27

I know I know, it takes someone from the community to do that kind of a list, the staff is busy with development so you can't blame them right.

Wake turbulence may not be optimized yet but I don't know about it enough. Acceleration lag is normal behavior. Depends on your CPU, don't expect it to ever be smooth unless you install 1 extra CPU each time you raise the game speed by 2 times :P Acceleration may improve after Vulkan API and *multi-threading* update. 16GB feels a bit like it's not enough RAM for what you're saying is a lot of planes. Get an overlay (MSI/RSST, GPA, etc) going that will keep a check on Commit Charge so you could see if you're going over the RAM amount (16384 MB) that means you're paging out some of the memory to Pagefile, unused memory is paged out ofcourse so if it's only a little bit it probably isn't hitting DCS that much but that can depend.

Game lock up? Freeze, Crash?

I like the asset stuff very much, it riches the DCS, i'd like all of those misc buildings, industiral, electronic, radio stuff mhm mhm ain't that good or what! ... I figured out I have to build a few showcase custom missions designed to be all-set and ready for me to quickly show friends/family/guests DCS, kinda instant action but not exactly overwhelming, more like to quickly change an airplane type scenario for as less waiting or fiddling time, so I can jump within a mission or load up another one all set-up. It happend on a few ocassions the set-up to show the sim took long and there's no way to show someone DCS in 1-2 hours, 30 minutes to get into it. Had a youngster over from distant family a few weeks ago, I scrambled the whole morning to do a quick mission with lots of targets, thank god I had the WW2 Asset Pack I bought some months earlier, in the end he flew for total 3 hours across 2 sessions and flew like A-10C, F/A-18C and a bunch of WW2 ones, I couldn't believe my self how much various content I filled into those 3 hours, I was basically "an instructor" that day and I was exhausted at the end haha. Having those targets look good and add variety will help out with these showcase scenarios.

Thanks a lot. Wait you're asking me for a track? I guess I forgot about it in the busyness of it earlier (or it got lost in the OT) Here it is: https://forums.eagle.ru/attachment.php?attachmentid=229195&stc=1&d=1583278297 The way you get out of the Black Smoke Black Hole in the end where the GPU is frozen, is to take a screenshot with MSI Afterburner, it does something to the GPU to interrupt it and that allows the CPU/Process to get out and switch to a different view. In the replay I do switch to a different view (F1) but ofcourse it doesn't work or would take a very long time so I did the same trick, but the trick doesn't travel with the track file, so you have to recreate it yourself, gametime is ofcourse all screwn up and down to a halt, it's a black hole :D Same thing can be achieved by using a profiler and disabling draw calls temporairly. BlackSmoke_F18C_BaseExampleSeaSky.zip

I searched the forum and didn't find mentions, there is an unreferenced mention in wikipedia. It feels ... finding utility in most unusual places is a good talent to have, creativity and improvisation skills can be a big deal in an emergency. And the rear tail mounted cannon ... I'm not going to start with "Tanker Module" ideas as we have them already, but an AI version perhaps one day seems a fair and realistic wish.

That was definitely a mistake, I was trying to avoid just that, but I wrote the second paragraph later in the evening, actually I think it was written in a span of two days so yeah ... sorry about that. That's why I kept using "The Developer" and other and I was about to start writing Stage2 of why it's good to not name directly, which I would have posted when I was writing an earlier post before this thread but my browser crashed, I managed to recover the text but haven't extracted it from the memory dump yet. I did not want to reference the external site directly but apparently I see now I forgot to remove it in one place. EDIT: Oh, I guess it's also about the drama seekers, perhaps I should have left it with that term, tho it's actually the same phrase President Putin used when he responded to the media about whether he's in a relationship with Alina Kabayeva. (I just know that from being a newshound and coming across it :p) So I thought it was relatively safe. I might modify some stuff but ... I kinda modify threads too much after I post them all the time. If I have to then sure, but I guess I won't use that again in this thread. I didn't even mean to discuss much further over the same points, rather more about solutions which is more appropriate for the official forum to discuss rather than go back and forth with them directly, I agree, we have a partial summary of the problem and that's it, I could have went over and made a list of all the posts from that reddit thread which I would argue against in various ways, I decided to only 2 cases. The thread looks big because of formatting but I made good effort to make it relatively short if I compare to my usual trends.

Syria in past days: Turkish Drone:

Well, there's lot of these small tricks that are documented across the forum and the modding guys who dig deeper know about it so you'll at least get help when you ask most likely, but also search the forum.

Great idea actually, I didn't thought of that at all when I discussed SAR (made a few big posts about it) on different occasions. Is that realistic tho? Doubt all airplanes have rafts ... but I could be wrong. Perhaps it may be quicker than trying to come up some sophisticated swimming animations (but then again the engine got updated for Super Carrier animations). It should pop after a while too, depending on weather, and if SAR is really implemented then pilot health/life and other things would also have to be simulated a bit ... but who's going to run a 3 day scenario for the pilot to starve without water, well actually there is round the clock servers I think so for MP it may make sense if there's a continious campaign or something.

They are not in the installation, they have been in user's Saved Games folder since I'm around here.

Exactly.

Okay .., yet we only have your word, this effect requires to be in precise position, it's not about seeing the smoke from any given location, if I look at it from the side it doesn't do much either, look that's fine, it's not that I don't believe you, but it's not that hard to take a screenshot. Update: Reinstalled AMD/ATI Drivers with Factory Reset (deletes all other versions, settings, device driver history) to 20.1.3 WHQL (from 19.5.2 I think) and kept at default settings as per usual, I don't play with GPU settings much in terms of gaming tuning, as I usually don't get bothered by aliasing that much, but I was using 4x MSAA in DCS. Well there's no difference, did a quick test (now I need a break, perhaps a day or two) same Black Smoke behavior, 4xMSAA or not. The only thing there's different is just the FPS min and max bounds shift higher up, but the big drop is still there.

Update: 1. Grim Reapers on youtube also mentioned they noticed this (the head guy's PC at least) 2. Okay, it's not stereo rendering lol, it's double draw call becuase it's one smoke effect for each engine. I just didn't happen to only try it with one engine, or had the chance to test a single engine'd one. 3. The difference in smoke color that I noticed on another borrowed machine is probably due to Monitor type, it's TN, and my is IPS, that would have a huge effect on it self, so nothing to worry about there. Reminder: Those pink lines don't mean necessairly anything's wrong or too much, it's an outline of the objects in that draw call, the area being drawn, you can see the white smoke has a lot of them too the same way black smoke does, but white smoke is around 20 times less demanding if I eye ball it, if not more. You can see the right engine contrail smoke draws being highlighted, while the left one is not, so they're to separate effects for each engine, makes sense ofcourse, but it kinda adds to a lot of smoke saturation that overlaps/shrouded that hopefully isn't being rendered, not a problem with white smoke as it never takes too much, perhaps that's what is happening with the Black Smoke, that all of the smoke objects are rendering completely, even if obstructed? But Black Smoke is more transparent seeming and perhaps that's how it is designed to make the desired effect look right depending on various conditions and amount of smoke. The Black Engine Exhaust Smoke looks totally different in design versus the White Contrail Smoke and Smoke Generator Smoke anyway, it's not just a color change at all. However the smoke generator on F/A-18C only sprays from the left engine, I do not know if that's by design or not. --------------------------------- --------------------------------- Allright if you say so, ... just you know it can be tricky as eyeballing it doesn't really work to good if FPS is above 100 at all times because without screenshots I can't be sure what you guys are doing. There is a suspicious case I've got captured where the effect would not have a FPS drop, I don't know what I did different, but I was using 1080p windowed here, but I was using it before as well, and the game was in mission-start-pause for quite some time, only when I did the active pause black hole it started dropping the FPS. Maybe some kind of a clue that it is a bug and perhaps only happens in certain conditions, perhaps the smoke is affected by environmental conditions, or that the FPS was CPU bound and GPU had enough headroom? I'll see later but I'm gonna need a break sometime soon. Now I'm finally going to update the drivers and see what happens, I didn't want to on purpose in the middle of testing to do as much here to have enough to compare.

How did you find that out, Windows tracing can be tricky, I thought that as well, but you really got to check that in the right tool otherwise it's can be deceiving. It may be true but a mistunderstanding, are you looking at Commit, is it over your RAM? Because Commit is what matters, not "In Use" or "Physical Used". Don't read some of those labels literally in Task Manager, compare with Process Explorer for example to get an idea, you'll see same numbers but a different name. (make sure you actually configure columns to show all of that)

That's because various variables are grouped to subitems in a tree-like structure, autoexec starts from the programs root level, so you have to specify the path, unless the variable is a general/global one. options.graphics.statsColor = {nnn,nnn,nnn} This should be the case for all graphics options. For other things you can get clues about this by just looking at the folder structure but this may not be a sure way for all cases. It can take a bit of trial and error.

Blocking would be the highest strength level measure, otherwise I largely support the OP's thinking and the discussions about this that will get us to get to some understanding and at least partial solution, it's good to debate because the players also have to come to an agreement with eachother and the larger communities, it should be a process that takes some time because habits can be hard to go against but this is something everyone with themselfs has to come to grounds to get some kind of balance, you can't be only enjoying in perfect conditions and using the latest and greatest and fastest. I wrote a whole thread based about that :beer: https://forums.eagle.ru/showthread.php?t=265404 Tho sorry OP if I have seen this thread before I might have posted it right here in a different fashion, but oh well now.

Reserved for possible updates.

The whole DCS reddit/dev/buggy/soon/openbeta/news/behavior stuff can be explained/remedied in a sum of a few points, at least partially the ones I have on my mind right now, I didn't want to go into a heavy write up in this case, so it's bullet points. There's probably more, but still, most of it is background noise, he said, she said, he though, they thought, of just chatter and stuff, but these things may all lead into common root causes or points which could be used to remedy the situation. (sometimes you can fix a problem in many ways so those don't actually count as the root cause, because kinda equal, its hard to say which one would be the root) ******************* OpenBeta Distinction: ******************* Community got used to the OpenBeta too much IMO. It's natural to use something experimental at your own risk, and complaining about it shouldn't be fair. Solution is to hammer the idea of OpenBeta/EA so that nobody forgets or uses an argument they didn't know about it or whatever. I have disagreed with the popular use of OB in the Multiplayer from the beginning. --------------------- Visual distinction: A natural repellant: Depending on various factors including the general community feeling, a balanced strenght level of this visual distinction could be applied to the OpenBeta build. A too agressive (high) strength of this visual distinction would keep the most amount of people away as it wouldn't allow them to use the product for purely entertainment purpose in the most comfortable of conditions, but that would make it count for a closed Beta so not that much. This visual distinction is a natural repellant for freeloaders and fake testers, the Developer does not need to use/waste any communication effort for this to work. Examples of visual distinctions versus Release build: Color, style and/or texture overlay of the general GUI elements that is not intended for comfort and denotes a development environment, a yellow/black "under-construction" pattern comes to mind or similar. Text indication overlay in all the options/settings pages Text indication overlay in the loading screens. Text indication in certain Mission Editor GUI elements. Text indication in the F2 View Status Bar. Other subtle indicators. -------------------- Legal distinction: Open Beta Disclaimer could be placed in particular on: Docs Forum FAQs Customer Support FAQ Main Website, before downloading the installer. In a dialog before first starting DCS OpenBeta, with an "I understand" and "Quit" button. Dialog resets every OB update, excluding small hotfix. (aka choice remembered until next update) As a shortened version in a recurring dialog after connecting and loading into a Multiplayer mission, with an "OK" button. In a dialog or console when launching the OpenBeta dedicated server, with an "I understand" and "Quit" button (Yes/No for console). Dialog/answer resets every OB update. In case of a crash, additional crash reporter text to add note that user was using OB when it crashed and it's to be expected, and that "consider switching to Release if this issue persists", etc, or something. What would the OB disclaimer contain? -- I kinda lost track of this paragraph, boy the way I write threads, not linearly, it's too late to fill some of my thoughts in right now, tired. ****************** Their own problems: ****************** This one is simply like how much communicational effort does the Developer wish to spend on some of the potential customers on those who don't follow any basic rules, fairness and disclaimers. They're not serious customers let them make up their own mind and hope new ones come.* Try to go out of bounds and use free time to play babysitter (what COO is doing now) Hope that they realize ony their own they may be wrong in their style of feedback or the logic behind them. *Core community plays a role and provides communicational support as usual, more or less, so even if Developer doesn't do anything the situation could remedy slowly/slower but it's not assured, new generations and new fresh players come all the time, more or less a general thing that is not DCS specific anyway. ---------------- Snotty Noses: It looks like some of these people seek to have a sniff at internal drama more than they seek a finished product and the primary content and service that is sold and provided by the Developer. That said, loyalty can be a double-edged sword, it makes the core community defensive about genuine shortcomings and other concerns, because when you do search for a treasue you may eventually find it while going through a ton of false positives, but not necessairly. If there is truth to the internal drama that Snotty Noses disovered as being the biggest root cause of all the issues everyone have with DCS then fine, so be it, it still depends on hard evidence tho, and if they believe it they can, discuss it now, but it's not okay to act like having free reign over everything and spam/bully/shout at others. The developer is still producing something that is not a life requirement, it's not the backbone of the civilization, it doesn't have to do with health/wellbeing directly, it's not the government, so they can't just demand things like that. The developer can still do what they want and sell it to whoever likes to buy it and who doesn't like it is a non concern for the civilization at large. If the loyalists have their enjoyment in DCS then so be it, everyone can decide with their own head, how they're satisfied, how long they'll be playing before they deplete the current session and motivation and are ready for something new, etc etc. We can give the newcomers the acknowledgement that they come from previous experiences where they have been treated relatively unfairly, but it shouldn't give them free pass of accusing without research and mirroring their habits, drama and the-way-things-work from over there. Pictured: A classic example of snotty nose behavior (top), as well as someone imagining DCS Developer being a character in a Japanese manga cartoon. (bottom) ---------------------------------------------------- Invalid and/or Unfair and/or Illogical Arguments: Some people want all the benefits. They want the latest possible, that is relatively stable in their own definition, and if it's not soon enoguh it's bad Developer supposably. So more testing had to happen in some public Alpha or internal stage-tow to do a longer testing procedure so the OB will be "more stable", while the time it takes to make OB less buggy would mean increasing the time it takes to provide the OB, so what's the point ?!?!? Infact, I do support the idea of larger internal QA effort, but with different context/reasons; (which that was unveiled in the last February newsletter), everything will take longer down the line, great ... but wrong, it won't take longer, it will take the time it's suppose to take. It's all how you view it, how you percieve it, is that piece of food more expensive, is it not worth it? I found eggs that are cheaper, I'll buy those, really, is that egg the same, does it have the same nutrient contents? Pictured: An example of a freeloder, a supposable tester who has no intention of testing anything. And that should be enough right here, you guys go ahead and discuss other solutions, and keept this sort as much already being done and said elsewhere.

I know but that's the hard truth, the term Beta should be respected and not just kind of a throw around term for another version/build. You have been infact blessed by the developers for not having to be bombarded with disclaimers and legal text for using OpenBeta as I think I already mentioned long time ago that It seemed to me the builds aren't distinct enough. I think it's about time that changes and it can be done as annoying-less as possible hopefully with understanding of the community, and this idea is for the good of all parties, my intention is not to be some wise guy saying this, I ultimately I care for health of the whole operation, so it's not like a demand it's more of a really good friendly advice I'm talking about here ... Maybe there is something already and I didn't happen to go refresh on that, I will later, I more mean that it should be notified, because in court you can argue all sort of things "I wasn't informed enough, ... OB looked the same as REL, ... hell do I know, I'm not a computer person" If one huge youtube channel does a review on DCS, you have a million people coming your way, you want legal cover regarding OB IMO, and if it's already there ... well it should be in your face, who knows what could happen in future once core upgrades start landing ... weirder lawsuits have happend "I played OB and I didn't get my patch on time and im sobbing now in my LA apartment, want damages in X amount nau!" And the perfect storm may be brewing, all the civilian aviation issues of automation unreliability, pilot shortages, 737-MAX 8 ( , , fuel tank FOD) environmental concerns blocking expansion of airport capacity (eg. Heathrow), and the coronavirus, all those travelers will be flying on simulators at home instead! kinda lol

It's your fault if you're using the Beta build for entertainment purposes.

Doesn't seem realistic to me.