0xDEADBEEF

Yes, in the settings screen below the image of the screen. This sir has finally solved it! Thank you very much!

Hey guys! I've just spent a couple of hours googling and checking forum threats and I have absolutely no success. I use a MSI GTX970 and set up shadowplay - seemed like an easy feat. However. It simply does not record. Period. first i would not even get the overlay - at all. I then checked the allow to record desktop checkmark, now I at least get the overlay, and the overlay says it is recording. I sometimes get the DCS loading screen pop up shortly, mostly after starting recording and after stopping it. However. There are NO files in the specified folders (neither temp nor save-folder). I'm stuck. I even tried to contact nvidias customer server, which seems to does not even exist for software :doh: Anyone got any hints what I can try or maybe someone had a similar problem and got it solved? (system is brandnew, latest drivers, fresh Win10) thanks! Edit: partially solved. I was using Win10 N without the Mediaplayer. Seems this also includes all videoplayback and other media-backend files that are needed to handle video in the operating system. Dowloading a mediakit (which took 3 attempts to find the only working most current dl on ms.com). It still only works with recording desktop enabled. If anyone has an idea how to get it working without desktop enabled that would be very much appreciated!

I have tried a couple of times now. I can confirm that the 120C launch warning is not reliable. Sometimes it comes (the chirping), sometimes there is only the lock warning without the launch. Also, sometimes the lock warning would remain if the bandit is splashed (F15). These findings are head on against AI with 0° bank angle. It would be very practical if the RWR would be fixed next, this seems to be the last remaining thing that keep the mirage from being useful in multiplayer. If you get Spamrams launched at you without getting a notification, this is a big disadvantage. While not on topic, it also seems the radar elevation in STT does not do it's job as designed, i would most of the time loose lock even though I notch less than 30 degrees.

Forget what I just said, this time I got the chirping sound from an aim 120B :huh: no idea why i didnt get it before ...

I just downloaded the newest update and was super eager to try it finally! :joystick: There used to be a launch-warning for the Aim120C that had some funky cirping sound. This time I only got the lock warning and was like, oh, I'm hit! oh, he launched? Is this the way its supposed to be working or are you reimplementing the launchwarning? Only getting the lock tone from an F15 and no launch warnign will make it quite difficult fighting them I'm afraid ... :huh: Oh and right after I was shot the game crashed with this dumped to the log. 01241.269 INFO DCS: try to write dump information 01241.271 INFO EDCORE: # -------------- 20160311-184857 -------------- 01241.271 INFO EDCORE: 01241.272 INFO EDCORE: # C0000005 ACCESS_VIOLATION at F3139577 00:00000000 01241.276 INFO EDCORE: 00000000 00000000 0000:00000000 01241.281 INFO EDCORE: F3139577 0014E480 0000:00000000 ?getTurbulenceInLayer@IAtmosphere@Weather@@IEBA?AV?$Vector@$02N@Math@@AEBV34@N@Z()+167 01241.283 INFO EDCORE: F313AFCF 0014E5A0 0000:00000000 ?getAtmoWind_w@StandardAtmosphere@Weather@@UEBA?AV?$Vector@$02N@Math@@AEBV34@N@Z()+21F 01241.284 INFO EDCORE: FF1FB772 0014EA00 0000:00000000 ?simulate@AerodyneFM@EagleFM@@UEAAXN@Z()+A52 01241.285 INFO EDCORE: B1DB37B0 0014EA80 0000:00000000 01241.286 INFO EDCORE: B1D97CC3 0014EBF0 0000:00000000 01241.286 INFO EDCORE: B1DE3E5A 0014EE70 0000:00000000 01241.287 INFO EDCORE: B1DE1AA3 0014EEA0 0000:00000000 01241.287 INFO EDCORE: 050C6CEF 0014EF20 0000:00000000 01241.287 INFO EDCORE: 050C7235 0014EF70 0000:00000000 01241.287 INFO EDCORE: B1F08068 0014EFE0 0000:00000000 01241.287 INFO EDCORE: B1F0CA35 0014F040 0000:00000000 01241.288 INFO EDCORE: B1F226A4 0014F070 0000:00000000 01241.288 INFO EDCORE: B1F225F4 0014F0A0 0000:00000000 01241.288 INFO EDCORE: B1FC756C 0014F750 0000:00000000 01241.289 INFO EDCORE: B1FCABC5 0014F790 0000:00000000 01241.290 INFO EDCORE: 10F08102 0014F7C0 0000:00000000 BaseThreadInitThunk()+22 01241.290 INFO EDCORE: 1301C5B4 0014F810 0000:00000000 RtlUserThreadStart()+34 01241.469 INFO EDCORE: Minidump created. 01241.471 INFO DCS: try to write track file

I dunno, but it had a DCS-wiki with very valuable documentation about the DCS-Scripting Engine. That's why I found the Mission Builders corner appropriate ... I'm using the Google cache for now, which does not work very well, but at least I'm getting to the most important information bits ... would be a real pitty if all that information was gone all of the sudden :(

I got no clue why this was moved to chit-chat, when it is about the Scripting Wiki ... The guys on #hoggit at freenode say it might be down forever. does that mean the scripting wiki is gone forever? "[22:27] <Lawlcat> oh the website [22:28] <Lawlcat> thats likely down forever [22:28] <Lawlcat> zelly is basically awol at this point"

You can also set this in the advanced settings when you create a new multiplayer session (Manual Pause, unpause without clients, and unpause on load) along with a couple of other settings. No need to edit the lua.

Hey guys! Dunno if this is the right place to post this, but I've noticed the hoggit scripting wiki is anavailable since yesterday? Does anyone know anything about it? thanks! Beef

while it may be a contributing factor I'm afraid it is not the source of the problems. The Buddyspike team is doing everything they can think of containing it. We will need to be patient until ED fixes this.

During testing yesterday I realized that most of the time an ejection happens twice or more on my Server. There are two pilots on two parachutes triggering two ejection events that I get transferred to my logs: 04551.500 INFO SCRIPTING: koEngine.debugText: koEngine.eventHandler(S_EVENT_EJECTION)6 04551.586 INFO SCRIPTING: koEngine.debugText: koEngine.eventHandler(S_EVENT_EJECTION)6 triple ejection: 07541.934 INFO SCRIPTING: koEngine.debugText: koEngine.eventHandler(S_EVENT_EJECTION)6 07542.033 INFO SCRIPTING: koEngine.debugText: koEngine.eventHandler(S_EVENT_EJECTION)6 07542.133 INFO SCRIPTING: koEngine.debugText: koEngine.eventHandler(S_EVENT_EJECTION)6 It is a little inconsistent, sometimes it correctly only one event, most of the time its 2, and sometimes its even 3 ejection events (and Pilots ejected from a single seat aircraft) (I'm logging every event that is triggered so I can learn more about when which events are triggered when). The mission is attached. The Kaukasus Offensive 0.66.miz

lets assume a Client has downloaded and installed the M2000C but does not have a key. The M2000 will not be greyed out in MP Slot-selection and if selected, the player will not be able to fly, but an AI plane will be spawned instead, although the slot is listed as Client in ME.

Aviation has always been and will always be imperial: Knots/Feet/Nauticmiles. Only the russians do their own thing. I feel you, I am metric too, but you will get used to those 3 units easily. I'm still struggling when i have to deal with pounds and gallons, but as long as you got fuel in the tank this does not matter a lot, and when you run out of fuel, fuel is out and you got other problems to worry about ;)

lol Caponi, hat er nicht. Die moderneren Helis haben ein SAS. Der Radar-altimeter ist ws. das komplexeste elektronische Gerät im Huey. Aber gerade das macht ihn doch so interessant. Sofapiloz. Vielleicht Denk ich am Abend dran dir einen Track zu machen. Ein paar grundsätzliche Tipps kann ich dir aber mitgeben. Zum einen ein wenig lektüre: http://www.copters.com/pilot/maneuvers.html Klingt mega langweilig, wenn man die procedures aber verinnerlicht und versteht machen sie plötzlich massiv viel sinn. Ein Heli will wie ein heli bewegt werden. Der Huey vergibt vergleichsweise viele Fehler, es ist trotzdem besser sie von vornherein nicht zu machen. Super wichtiger Punkt ist attitude-flying. Eine Referenz am Hubschrauber zum Horizont vergleichen, um die Bewegungen vom Hubschrauber besser zu erkennen. Uns fehlt im Sim nunmal das Popometer, je besser wir das kompensieren, desto einfacher wird das fliegen. Ich schätze dir rutscht der Arsch genau in dem Moment weg, wenn die engine anfängt wieder Leistung zu liefern. Das erfordert gutes Timing und Gefühl. Ich empfehle nicht auf die Torque-Anzeigen zu schauen, du weißt eh dass der Drehmoment kommt, und du bekommst einen sehr guten Audio-Cue wenn die Turbine hochläuft. Während der Geschwindigkeitsreduktion läuft die Turbine mit sehr wenig Leistung. Je später du am Collective ziehst, desto spontaner kommt die Leistung. Versuch die Turbine zu hören (im Echten würdest du es auch spüren), sobald sie hochläuft drückst du sanft ins Linke pedal und gibst gleichzeitig den knüppel ein wenig nach links (der Heckrotor will dich nach rechts schieben).

+1 on leaving the scan zone where the contact was lost. Kudos for your great work Razbam! Can't wait to try the radar (hopefully) tomorrow!

Oh yeah, once last thing to point out: we had a very interesting moment on the finals, when we captured Tiblisi, and blue was seemingly still able to spawn aircraft in Tiblisi for a lot longer than 5 minutes. I suspect a glitch in the code enabling them to do that. Maybe you can have a look at it. I didn't see it myself, but there were constant reports of this happening in TS.

Ahhhh this was the best blueflag ever! (and the worst at the same time, but that certainly not blueflags fault). Huge thanks to everyone who spent so much time putting this together! The value this game-mode addds to DCS is just indescribable! I also enjoyed it heaps to fight the 104th so much. I have to admit that your teamplay-displays were nothing short of amazing to watch. It was great learning fodder for me everytime I got taken down. Can't wait for the next time! I gotta admit too I was suprised that after all balance was quite even, not even close to what I expected it to be. This is a very good sign. I also think there should be a max-players per team cap, and I agree that this limit should be a soft as possible. Ideally, if red and blue have an even pilot-force of 60/60 ready to fly, it is not good if the actual player diversity on the Server is 45/15, just because one coalition was faster with getting pilots online ... I have trust in the buddy-spike team that they will come up with a good solution for this ;) Also kudos to the blue-team to show red the difference between being organized and not. Especially in the first week I think you guys outperformed us not because you were the better pilots (you likely were) but because you got everything organized better than red. I'm glad we could learn from that in the second week and strike back. I would not deny the fact that a lot of blue pilots lost motivation after a lag-fest or two in the second half of the second week and I personally find it a pitty. I would not have minded outnumbering blue less than we did, although this would have reduced hour odds at bringing home the victory. Anyway, putting all emotions apart. Blueflag 5 was simply amazing! Huge thanks to everyone who contributed, participated and sacrificed! Last but not least, i would like to point out bootysweats performance on the very last day. This dude was hauling fuel nonstop in Pak3 while we were doing the final push. After the last server restart before the lag-nuke I was off the helipad enroute to Vaziani within 1 minute, going max speed with emergency governor on. 5 minutes before I arrived Bootysweat delivered the first load of fuel to Mozdok, which I found was a very funny moment :D (we really had enough fuel to go through the last push) I think this guy deserves an extra medal for that! :thumbup:

I didn't even know you could do that :huh:

Yeah, its weird. I was told its gone after you reconnect, and I wont get in ...

I'm afraid the fact that we're all human keeps this from happening. But I'll do my best to comply with your request!

So 96 connections are enough to DDoS DCS ... no I'm not going to say what I was about to. I think I'm going to send prayers for improvement instead, even though I usually dont do that, maybe it helps ... Thanks for your hard work ciribob and the team! Love what you do!

besides not the server itself being the problem, 8 core would not help much more, as dcs only utilizes 2 cores (1 for audio) Dont take it as an offense, but if we also count how many times the server sometimes restarts before its actually running longer than 2-3 minutes, 30 is not very far off the shot. And I have not witnessed many server-rounds that lasted the full 3 hours. Again, this is no attack on you, just facts layed out, i am very aware that you guys are doing the best you can and I cant thank you enough for that! :)

To add something positive to the whole discussion, you guys have created something that keeps people busy although the foundation you built it on crashes about 30 times a day. This is a remarkable achievment and I would like to thank you for that once again. Your efforts are massively appreciated!

While I really like the idea of the fuel system, I have to underline what others say. It creates artifitial imbalance, and with the server-instabilities it simply kills gameplay and motivation for red and blue. I hate to say this, I really like the idea, but it is far from balanced and what it does the most is keep us from having fun (and I'm not talking the other issues we can only solve with patience). We would need an army of choppers to keep the north-east supplied especially taking the crashes into account ...

Even if we would assume the scripts are the cause, DCS should be easily able to handle it. It's no complicated maths and we have i7s and SSDs. Once the problems are resolved, the scripting engine will deliver us a lot of joy, made by the community. I see blueflag as a taste of the future of DCS. Yes, I'm rather new and overly optimistic, I know. I like dreaming :) I can only second that!