All Activity

Awesome thnx a lot

In this case, there was a substantial Germany update and IIRC recently also big Kola and Sinai updates (not sure if they'd have been since you last updated) but very plausible with maps that it could be 149 GB. Fortunately most of that will replace existing, so you shouldn't need fully that much more space on your drive.

Tested in both F18 and F16. Same issue of looking over right towards back of aircraft. Jitter is very apparent but smooth when looking over left should towards back. Used arrow keys to look and its smooth in all directions so it has to be linked to TrackIR somehow.

Visible wingtip vortices are a function of the humidity level in the air. I don't know for a fact, but I doubt that DCS factors in humidity in causing wingtip vortices to be visible (don't think humidity level is an option in the Mission Editor). As a default, I suspect DCS just programs visible vortices to appear anytime that you put a G-load (greater than 1) on the plane. Not at my computer right now to check, but it seems (based on memory) like visible wingtip vortices may decrease with altitude in DCS. I'll check that later to verify. However, I was doing some AAR yesterday with an F-16 behind a KC-135 and there were visible vortices coming off the tanker wingtips at 28,000-ft MSL, but none off the F-16. I flew my F-100 from Vietnam back to the States in late September 1970. Here is a picture of my flight refueling behind an KC-135 at around 30,000-ft MSL over the Pacific. No visible wingtip vortices on any of the planes.

sorry the truth and the law are on EDs side. RB is in the wrong here. They violated the contract, and got caught. But instead of just owning up to it, and agreeing to a new contract with ED... they threw a temper tantrum and stopped all work on the modules that people PAID FOR, and then AGAIN violated EDs contract by not handing ED the source code so THEY can continue the work on those modules and keep them working.

I did not think of that. But whats the difference if it loads your default.dtc on cold start, or if it loads none? If you will change your settings for that particular mission you would do it anyway, no matter what was loaded before.

And NOT using the Comms menu is currently where the problem lies. Although I have seen at least one report that Case 3 still crashes, but as long as you call at least inbound you shouldn't CTD.

Agree it would be good that you should be able to create a default DTC that will be loaded if you don't pick another one. Also agree with it being loaded on hot start. But I don't think it should be automatically loaded for cold starts.

Am einfachsten wohl über die Nvidia Software. Kannst nen Hotkey für record/stop setzen und so dann ingame Sachen aufnehmen. Werden dann in den festgelegten Ordner mit Format XY gespeichert.

Tested flying 180 degrees in opposite direction to make sure it was not terrain or clouds doing. This happens flying and on the ground. My FPS does not drop but there is a very apparent jitter. This jitter does not show up in the trackir interface. Running 120hz. Any ideas? TrackIR Jitter over right shoulder video

Create an autoexec.cfg file with the content below and place it in the Config folder : if not net then net = {} end net.allow_unsafe_api = { -- this defines the secure zones where net.dostring_in() should be called from "userhooks", "scripting" } net.allow_dostring_in = { -- and this defines the scopes that you want to use from net.dostring_in() "server", "mission", "gui" }

You're using the EASY COMM's binding and REALISTIC COMM's is enabled in the mission. You need to use "Transmit Switch - UHF (call radio menu" (or the VHF version) rather than "Communications Menu". Works fine when you do that. You should get UHF Radio AN/ARC-164 above the radio menu that pops up. When you're using the Communications Menu binding you won't get that.

My thoughts and hope on this is: - I’m not expecting Razbam back - I’m hoping that the initial agreement between Raz and ED was purely about the argument over payment to Razbam and the potential issue about intellectual property - if the above is true, that it might still leave the Harrier, M2000, Mig19 and F15e modules as IP property owned by Razbam. If so, then may be Raz could sell the IP/source code to ED or another 3rd party, who could then take on responsibility to maintain and also the opportunity to start selling them again. Being realistic, I’d be a bit skeptical of the sales potential for the first 3 of the modules that I mentioned, despite owning and liking them all. However, I’d happily buy the F15E again, and for a developer who fancies getting into DCS, it might be a good way to open some doors.

Latest release: v0.27.0 This version of Livery Link will now check inside nested archives for liveries. This is useful since some livery authors place several Zip/7zip/Rar files inside a single archive. This option is enabled by default, and can be disabled from the Tools menu. Livery Link will only ever extract valid texture files and description.lua files! https://github.com/Camble/LiveryLink/releases/tag/v0.27.0

Pretty sure @SPOOKY 1-1 put out a single modpack to use with his hosted version of ITJ. Not really a solution, but it's a way to dodge the problem!

Thank you ouky1991 for such a quick remedy to the HUD mod, I've been using your F-16 HUD mod since it started and now can't live without it, a essential realism mod for the Viper and Hornet.

Based on there current rate of updates 10 to 15 years

Can confirm I have an issue with DCS crashing with both F4U and F-18 when landing without comm's. Happens on MP servers and Instant Action carrier landings.

All my laser bombs and missiles miss. Sometimes 1 bomb can hit the target, but I think it's a coincidence. Is it like that for everyone? track 62Mb https://dropmefiles.com/Rqbrd

This module and all other Razbam modules are essentially unsupported. Unless this bug is on ED’s side it won’t be resolved.

That's called an engineering solution.

I can fly the F-4 or any other aircraft perfectly fine in singleplayer and multiplayer on my own. But as soon as my buddy joins my crew, I cannot open the Jester UI or the grease pencil. Opening them causes immense lags - like a frame every 10 seconds or more - and eventually my game crashes. I'm also experiencing some occasional mild lags while flying which I'm certain are also depending on another player being WSO or not. Is this a hardware problem on my end or....? My specs: AMD Ryzen 5 5600G RTX 4060 Ti 48 GB RAM For some reason I only have one log file which is of my last flight in singleplayer - after today's multiplayer flights. In that log it says "Out of memory in ed_malloc for 436694070960 bytes." which is an error I've been having for some time now but it hasn't caused any issues after fixing my pagefile. Is that the thing causing issues now as well?

VLC Mediaplayer?????

Hi felixx75, if it's not too late, suggest you take up Rolds on his offer of a bet. I've copies of pilot's notes for three variants of the Mosquito, including our FB VI, and they all clearly state one quarter throttle. Publication dates range from Aug 43 to Jan 50. See attached excerpt from the Jan 50 notes for the FB6. If when Rolds' says "someone misinterpreted it" he means the devs, seems to me they've got it right. If he means the pilot's notes themselves are wrong, I'd suggest the odds of an error there persisting over seven years seems pretty remote. Particularly when the horn in question is so aggravating.