TheBamse

Great update! All my previous "issues" (again, caused by me, not SWAPR) was solved with the new version. I'll put the updated mission on our training server for "public" testing today!

Oh, forgot to write it here to but after sending Hardcard my mission it was a classic case of "damnit, of course" and I had placed units inside hangars but that didn't show as hangars in the ME and I was to sloppy to check each unit in-game to realize that was the case. So, it was not a SWAPR error, it was a Bamse-error :D @Hardcard the upcoming changes sounds amazing! Can't wait to try it out when it's ready! :D

In theory it's pretty simple, just add more strings to a table, like this: (from the reference builder as an example): local AI_SET = SET_UNIT:New():FilterPrefixes({"Prefix1_","_Suffix2","string3","etc"}):FilterOnce()

Correct, mission is Caucasus based. I'll PM you the mission in a couple of hours, don't have access to it atm due to me being at work :)

You are one certified beast! I'd like to chime in to the other praise too, you are currently doing one cool as hell implementation to solve a age-old "issue". I really do appreciate what you are doing! New version of Reference builder works much better (I get all client aircraft enumerated in the counter now, but still "only" get 39 in the log to copy&paste)

I also ran into the issue where not all aicraft gets enumerated. In our mission I've never been able to get more than 76 slots to get enumerated by the script and the wanted total is about 115. There seem to be a set of aircraft that it can't enumerate even if I remove others so I'm currently messing around to see what the blockage is. I'm only using parking spots on Senaki-Kolhi and Sochi, no FARPs or freely non-parking spot placed aircraft. Total unit count ~300. Latest version of the reference builder mentioned above I get an error on line 56: 2019-08-04 19:37:25.074 ERROR DCS: Mission script error: : [string "<edited path to reference lua>"]:56: attempt to index local 'ClosestFARP' (a nil value) stack traceback: [C]: ? [string "<edited path to reference lua>"]:56: in main chunk [string "assert(loadfile("<edited path to reference lua>"))()"]:1: in main chunk

I was definitely having a latched laser when flying yesterday. I even forgot to pull the trigger to turn it off sometimes so GBU-12's were tracking way way too early (very easy to see in F6-mode) and ended up super short. (reading the white DDI text when in black hot = impossible sometimes ;P) Once I pulled the trigger again so LTD/R changed to L ARM again, all good. After being a bit confused by the Wags video stating that you need to keep trigger pressed I did this test several times on a laser code I know wasn't in use by anyone else and the behavior was the same, repeatedly. 1x trigger = latch on/GBU-12/AGM-65E tracks 1x trigger = off/GBU-12/AGM-65E stops tracking rinse and repeat. Sure, if I was holding down the trigger ordnance kept tracking too since it's the first trigger pull, but i had to release the trigger and pull it again stop tracking so for me when LTD/R is showing it's lasing. This was all in MP running DS (even tho I should know better), latest beta, 4x F/A-18C human players against AI.

Oh please GOD let there be a fix to the tasks resetting bug and the DS --norender bug included in today's patch .... and that it's a matter of many of the huger items often being left out in the first couple of iterations of the change log. please please please please :)

Oh, so running the DCS DS on Windows Server is not supported and HAS to be installed on a client OS to be supported, while the OS-dev doesn't allow the client OS to be used as a server and therefore cannot be used? Oh hark the bells of catch 22 :D I'm grabbing my popcorn right this very second.

It's a behavior reported in other threads but hasn't been picked up by ED as a confirmed bug yet. You're in the same boat as the rest of the ppl experiencing the same issue. Respawn and try again until ED confirms it as a bug and fixes it. The more info you can give the faster ED can determine where/how/when and almost no bugs are accepted without track files or video showing the issue so make sure to attach one of those :) If you have any mods installed, be sure to disable/remove them before creating track/video.

Damn, that's cool. Good job!

We have a 24/7 training mission up and running on our server. Server is still running the old "client based" DS (not the newer stand-alone installer). Same mission on previous OB were using about 4-5% CPU at any given time no matter if we were 2 or 10 ppl on doing all kinds of traning-y stuff. After updating to 2.5.5.31917 the server starts with 15% usage (maxing one core) and never lets off. Kinda like the times before when DS wasn't around :/ Granted, the mission is quite scripted and a lot going on, however even starting a completely blank mission and just placing some client aircraft on whatever airport and 2-3 RED AI Su-27's in the air with no scripting done the CPU usage is higher than running the much heavier mission on 2.5.4. Something was definitely done :)

BuzzU: well, the Glock lower outer frame is made of polymer atleast. Slide, slide rails etc is made of metal ;)

Thank you for the very detailed reply, much appreciated!

how would one go about using the Rift S with a pair rather large over the ear-headphones like the AudioTechnica ATH-M50x or Beyerdynamic 770/880/990? Is is just a clear case of nope or "just" uncomfortable? If nope, has anyone head of a 3rd party headstrap or something along those lines? The reason for asking is that I don't want to spend $$ on a pair of IEMs that I already know I'll only use for DCS and nothing else.

Even with the above posts made by Wags in mind, I still do want to add my voice to the group showing concern. Speaking from a small ~10 person group where about half of us likes and flies Navy stuff and the other half is flying AF or non-US aircraft we will not be using the Carrier DLC due to us not wanting to split our group in two. I will however donate to something we can (and do) use; MOOSE and the AIRBOSS-module matching the price tag of the carrier module when made available. I am looking forward to buying other modules that encourages and supports co-operation instead of the opposite tho!

I was very able to drop about 16 GBU-38's yesterday on our own server running 2.5.4.30386 both on clients and server using PP MAN mode, using nVidia driver v430.64 I think more details are needed, because de-facto; it's not a general openbeta issue otherwise it would happen to me/us also.

Edit: Ninja:d :) First of all there's no data link on the BRU that carries GBU-1x's so there's no way to use the bomb as a sensor to feed the targeting computer with a solution. Second, the laser isn't always on prior to pickle, it will most likely only be active some seconds prior to impact so it's not a good way to get a firing solution. You don't _need_ a WP but you need a target of some sort that the aircraft can feed to the targeting computer. Without AG radar or TGP, we only have waypoints and the currently hard to use HUD-designation and I'd go for creating a WP any day of the week out of those two options :)

1: We do not have our liveries on our server (and never had, pre- or post dedicated server) and they show as they should for all clients that have them installed.

Maximum release range behavior is one thing mentioned in the video and not in the changelogs. But, any DCS player that's been playing for more than six months knows that the changelogs always lacks info on it's first iteration. Always always always always :)

It's been like this since day one and has not changed, CCIP and AUTO-release is always calculated for retarded release in HUD no matter what mode you put the bombs in. It was reported early on and sporadically here and there for about a year, some threads got acknowledged, some not and I've tested about every other OB release since then and results are as they've always was and it is still an issue in 2.5.4.30038. Not a priority issue maybe but it's still there :) Referenced threads: https://forums.eagle.ru/showthread.php?t=237527 https://forums.eagle.ru/showthread.php?t=232239 (NineLine confirms the issue in this thread but a bit unclear if the reported bug was the bomb fall line being wonky or the FF/RET-issue) https://forums.eagle.ru/showthread.php?t=216786 https://forums.eagle.ru/showthread.php?t=211247&page=3

Oh, right, gotcha. I forgot about that one, my b! Then my answer stands for the rest of the bulleted points :)

The mod has nothing to do with the aircraft you are in, so yes it will "work" with the A-10C :)

yes please! :)

gunterlund: configure your tacview. it has nothing to do with DS.