codefox

Das "löst" lediglich deine Kamera von ihrem Punkt im Cockpit, so dass man sie frei positionieren kann. Aussteigen des Piloten (bis auf Strg+3x E) ist bisher nicht möglich.

About to buzz the tower... Guess how it ended? (cockpit view in description) [ame=https://www.youtube.com/watch?v=WzcoUSwZhiM]Video (cockpit view in description)[/ame]

Known bug with 2.0. http://forums.eagle.ru/showthread.php?t=165887 Looks fun, I gotta try it when I get back home.

Funktioniert bei mir auch mit Fullscreen, sofern Desktop Capture aktiv ist. Falls ShadowPlay oder der Windows 10 Recorder nicht verwendbar ist (zu alte Grafikkarte oder was auch immer), leistet Fraps auch gute Dienste.

Renting servers is already perfectly possible, we're doing that. All you need is a somewhat recent CPU to run the server. Strongly agreeing on wanting a dedicated server, however :)

I will give this a try on our NTTR test server and post in here if it changes anything on multiplayer as well.

We are seeing a similar issue on our DCS servers. Currently, we got two servers up and running (Virtual Aerobatics for Caucasus and Nevada). Hardware specs: CPU - Intel i7-4790K RAM - 32GB SSD - Samsung MZ7LM240HCGR 240GB (really fast!) Internet connection - 250Mbps up/down We are still frequently seeing stutter issues on NTTR where the server(!) freezes for a few seconds. This causes every client to freeze too. Same issue on the Caucasus server, although it happens much less frequently. I doubt these freezes are about file loading.. at least not about reading them from the disk - rather processing them inside of DCS. Also, as we disabled 3D rendering and all that stuff, I also doubt it is directly related to rendering 3D models.

ED stated multiple times that they're not going to develop any more FC3-like modules. Everything following now will be full fidelity. Also looks like you chose the wrong forum, this one is for the old LockOn FC. Here is the DCS FC3 one: http://forums.eagle.ru/forumdisplay.php?f=321

Is it being streamed somewhere?

I turned both off. The MiG-21 has setting in the special options for cockpit shake, turned this to zero and the head movement by G-forces to off, still having violent shaking. Reminds me of a bug with the Mi-8 when you start to descend where your head also moves abruptly.

Damit liegst du schon so ziemlich richtig, bei der C-101 z.B. ist es einfach ein draw-arg das gesetzt wird und dem Flugzeugmodell noch eine GPU verpasst. Daher kam vermutlich auch der Fehler, bei dem früher manchmal die GPU mitgeflogen ist. Die Radvorleger bei der L-39 beispielsweise kommen auch über ein draw-arg an das Flugzeugmodell.

Yes we will.

Slightly off-topic but keep in mind that Starways textures are a separate product. ED will update Caucasus for free at one point and they said they'll keep updating it.

Yes, as I mentioned the Flanker is also more or less capable of doing so, depending on weight. Been parking it on grass every now and then. Never tried the Frog for that tho. Seems like most 3rd party modules are affected by weird ground physics regarding unpaved surfaces, as you can see with the Gazelle for example.

The prop planes are among the only planes in DCS that are able to land and takeoff from grass or dirt. While I agree that most of the fighter jets modeled are indeed unable to move on grass, I know that some specific planes would be able to but aren't in DCS, talking about the F-86, MiG-15, L-39 and, yeah, the MiG-21. Perhaps even the Flanker could move slowly on grass but that's even working in DCS, depending on weight. However, this all would not apply to every field IRL.. only those maintained to be more or less flat. Edit: Another thing is that the A-10C is totally unable to land or takeoff from the desert on NTTR.. that should also be possible.

In case you want to calculate it yourself, grab the coefficients off here: http://www.ngdc.noaa.gov/geomag/WMM/soft.shtml I'd honestly just go with fixed values for each map for now. Won't be much of an hassle to maintain since the amount of maps for DCS will probably not get all too high.

Es gibt unter den Schaltern für die Batterie usw noch einen, da steht "DFBR" oder so drüber. Der sollte sich eigentlich bewegen. Beachte dabei dass die Magnetic Brake auch ein Trim-System ist. Die hält deinen Stick der Position, in dem du ihn gelassen hast (so wie bei der Huey, Mi-8 etc). Dazu gibt es ein zweites Trim-System das wie bei Flugzeugen funktioniert.

We are now trying to run a second VA server for the Nevada map. It is up and running since yesterday, the mission is still being adjusted but overall it is running very smooth. Give it a try if you're around on NTTR! Both are running simultaneously and we will gladly keep the Nevada one running if there's a demand for such a server, granted that it's all going smoothly. In case you got any ideas for the mission, don't hesitate to let us know! Automatic server restarts are scheduled every 4hr, being on the same schedule as the 1.5 Caucasus server. Have fun and enjoy your stay.

That's what I wanted to say :)

I don't see anything to worry about in the log file. Does the problem affect every mission? I heard about some server list issue with faulty missions but never experienced it myself.

We've been having two Kuznetsov carriers on our server spawned as static ships. Now, while testing in singleplayer, I was not able to see either of the carrier in the ATC menu (as it's probably supposed to be since it's a static object). However, when I connected as a multiplayer client, I was given the option to communicate with the static Kuznetsov. Now here came the problem: as soon as I send any request to it, the server is going to crash. Reproducible every time. Due to this bug we are sadly unable to keep the carrier on our server but at least we found the reason for the server crashes.. Log and crash dump attached. crashlogs_kuznetsov.zip

That's a known issue, when a player's gear gets damaged others can not see it anymore, at least on some planes (A-10 being one of them).

So far I looped every helicopter in DCS and I'll hope to keep it that way. :p

Take a look at the text on the switches, I think now it is correct. Has been wrong before this update.

I was not saying I couldn't fix the issue but I rather wanted to express my feelings on this subject. I can not see any reason to disallow editing some files completely.