okopanja

the instructions do not work anymore on JF-17?

No you would connect immediately without waiting for the livery download. During that time you have drawback of using default livery, but afterwards it would be replaced the same way it get's loaded and replaced whenever any player changes the livery(this is how DCS works already now). As for 10-20GB: yes you can reserve even space, or simply let it fill in and if there is not enough space the game deletes the livery that was not recently used (Least Recently Used).

Why not installing liveries on demand? You login to the server, and your client figures out you do not have the livery for one player? DCS displays you low-visibility livery from default set, while in background downloads the correct livery, stores it in your local livery cache. You would be able to define the size of a cache. E.g. 10-20GB, and the non-used liveries would be deleted based on LRU (least recently used) principle. Benefits: you consume less disk space on clients you get to see all liveries "no cheating" (you ensure the least visible used be default before download & load completes) Drawbacks: ED needs to work to implement this. Either way if they aim for world coverage, streaming of maps is something that will surely be on their roadmap. ED gets larger traffic bill for their infrastructure (people keep downloading from them) your livery is not immediately available on first encounter. Some small amount of resources get consumed on client to download and load.

Making the other players aircraft easier to see in a way they don’t suspect? That’s a cheat/exploit in any other CFS game. Further explanation shouldn’t be necessary. Please see what I wrote later than initial comment.

Another approach would be to determine if there are common textures used in multiple liveries? Now, we all know that graphic designers do not care how many megabytes the livery will take, but they tend to be Mega-pixel-click friendly for everything to look better, and as consequence spend around 0 time thinking if this has impact on disk space or game performance. One could argue we could have several approaches, e.g.: 1. de-duplication of existing liveries, which might save perhaps 30% of disk space. This is essentially some intelligence applied to present strategy, Would need to be enforced by ED, and all liveries are still show to everyone. 2. ED defines mandatory livery pack, if the person wants he/she can download additional packages, either as bundles or specific aircraft. If the livery is not locally found, use the default low visibility from mandatory pack 3. ED defines mandatory livery pack, if user wants to use something extra he downloads additional packs, the viewing user when encountering the user using fancy non-mandatory livery is displayed the default low visibility livery, while in background without affecting performance too much the livery get downloaded and stored in local cache based on LRU algorithm to ensure that disk space is not overused.

Why would that be cheating? Simple map to module default. Each and every new module adds more and more irrelevant garbage by adding more and more liveries that ever were.

Note: this is not about AI, this is about multiplayer. As far as I know, this affects all aircrafts. Not just Viper/Flanker.

I did not expect yet the fix, but I tested just in case: still the same behavior with 2.9.1.48111

Issue is still not really fixed, just mitigated. ED needs to obtain separate certificate for https://dcs.world or disable the SSL interface on that SNI. @silverdevil at this moment http://dcs.world redirects to https://www.digitalcombatsimulator.com/ which is OK-ish Notice http vs https. In general the site has very decent A grade at https://www.ssllabs.com/ssltest/analyze.html?d=digitalcombatsimulator.com (this page if not cached will take 1-2 minutes to generate), but not the A+. However, noticeable is the usage of weaker TLSv2 (TLSv3 would be better) and encryption algorithms (they need to disable some):

Altitude is reset to 0 now. Thank you very much for the rapid fix, but I also found out that it is not 100% fully reset in case of hemispheres. E.g. on Caucasus (N and E hemisphere): 1. Enter the coordinates and intentionally set wrong hemisphere for that map, e.g. W and S instead. 2. Clear the waypoint 3. Enter coordinates for that waypoint again, they will default to W/S. I would expect it to be E/N In contrast untouched waypoint will have E/N by default, so therefore the re-entered waypoint should behave the same way as pristine waypoint. One question that remains it the following: Which hemispheres will be default in e.g. Caucasus, Nevada? Would that be E/N for Caucasus, or W/N for Nevada (since customer may be in a different hemisphere)? Or it will always be E/N (since both Pakistan and China are there)?

I would say this issue is fixed. However, it remains to be see if the new entry of geo coordinates should be: - N/E as default - N/S W/E depending on what the map default is. (Someone flying the same hemisphere would prefer preconfigured airplane to default based on where the country is). Not sure how this was solved in other modules and real aircrafts.

Interesting, e.g. I personally wanted to switch my VKB profile on airframe change, except for now that software does not allow it yet. (trying to get them to listen and provide at least command line tool).

I would write 3rd function with the real logic and call it from onShowBriefing/onPlayerChangeSlot. onSimulationResume gets triggered in other situations as well. E.g. pause/resume Also, check how it works in: -SP - MP on your own PC - dedicated server (with paused and unpaused mission) If it is not a secret: what are you trying to do?

There is no documentation, but it's there in ED's code. I faced the same issue and resolved it with onSimulationResume, but that was before I found out onShowBriefing. I will probably switch to the later, since it appears to be more reliable.

You can use: onShowBriefing() It will be shown when the user has already selected the aircraft and advanced. Briefing is shown at that moment

2 more locations: C:\Users\XXXX\AppData\Local\DCS.openbeta C:\Users\XXXX\AppData\Local\Temp\DCS.openbeta

1. Not really a problem when you gain access to documentation and you know where to look for and you happen to poses the electronic base 2 gens more advanced than opponent. https://en.wikipedia.org/wiki/Adolf_Tolkachev 2. Su-27SK manual explicitly states inability to relock. Apparently the missile is primed before actual launch through main radar's side lobs. If this is true, on relock it is not possible to synchronize missile anymore. 3. You can use TWS2 mode with Mig-29С but, upon launch the target it will switch to something akin to the DTT with addition of triggering the RWR warnings. I asked this some time ago and did not get straight answer, but perhaps another case of point 1? 4. Comparing the radar equation results between host radar and missile seeker on one side and active missile radar on other side would probably show the advantage of second variant (not to mention the benefits of having more freedom to stay out of range, or network-centric tactics). Also note that limitation of R-27ER range, does not come from the engine, but rather from the same power generator as used on R-27R, which limits operation to a maximum of 60 seconds. It should be noticed that certain slides on radar operation of dubious quality circulate around. The translations into English largely amount to techno gibberish. Also note that we are talking about early 80s tech vs late 90s up to 2006-2008 on the other side. E.g. during this long period 10+ generations of CPUs did proliferate. We are talking about having limited resources of e.g. F-15C/Flanker radar computers able to display only simple shapes on HUD/MFD compared to modern stuff (15-17 years compared to nowadays).

https://wiki.hoggitworld.com/view/DCS_hook_onPlayerChangeSlot

The main problem is that when you join 2 metal materials, the join is never perfect. The resistance will some somewhat higher, but worst is the forming of so called parasitic capacitance. These can interfere with the signal. Even worse when you do it with 2 different materials. And btw: soldiering is not quite bendable. Do it properly or you will suffer from inexplicable connection losses.

Ethernet cables are not re-soldered, ever. Even if you succeed you will not end up with cable of high speeds. Ethernet cables are pressed together with special tool. If you need a longer cross over cable, either buy one finished or buy connectors, cable and something like this: https://www.amazon.de/LogiLink-WZ0012-Netzwerk-Werkzeug-Tasche/dp/B003Y3S0U2/ref=sr_1_4?keywords=lan+kabel+zange&qid=1699783293&sr=8-4 Here:

Tip: create mission to replicate and upload trk. Without that bug report like this is worthless.

Here is the normal log when running interactive. Service approach hangs at the moment of this log entry: 2023-11-10 23:12:49.382 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1024, 720] I suspect it's that new nvidia splash screen. Now I will remove both mods I have since both have EFMs and retry winsw dcs.log Still the same: even when clean with no mods it hangs. I am surprised there are not more complaints. I suspect people are not running DCS as windows server. One more thing: I do not use system account to run service, but the same account that runs the DCS interactively with no problems.

I am having identical issue with WinSW, I ran multiple variants of configuration parameter with identical log as the original reporter.

@Flappie I believe I already have modular server, since: 1. my installation is only 28GB 2. I still have the original DCS_World_OpenBeta_Server_modular.exe and it is binary identical to the one I just downloaded. Meanwhile I have tried following: 1. did slow repair: completed with no reported issues. 2. configure it to run with the service wrapper WinSW from: https://github.com/winsw/winsw I tried several combinations of start folder, modes and parameters and the reproduced problem is still there: it gets stuck in same place at 100%. Please merge my report into following topic, since this is identical issue. It gets stuck in the same way with just a slight difference is that at the end he gets: 2023-10-19 17:23:17.112 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1024, 720]

Dudes, how about both stopping at this. We all know it's not good enough and that this is just first iteration. Let's wait for the next version ED releases.