All Activity

I think it was nearest one. But i will re-fly this mission anyway so i will check this moment.

Update 250607A pushed to the user files https://www.digitalcombatsimulator.com/en/files/3344152/ - AJS-37 Support added (Yes, I'm aware and know how to use the DTC functionality) - Coordinate load speed improved for the Hornet -- AJS-37 Viggen Only B & M waypoints can be added. Bearing and range for offset points can be manually added. Waypoint Sequence Start can be used to specify a startup waypoint and route. Default is 1 Examples: Set WSS to point 3 : @<3> @|#| ... will load/replace the next B point in the load sequence @|B| ... will load/replace the next B point in the load sequence @|M| ... will load/replace the next M point in the load sequence @|B3| ... will load/replace B3 point @|#|N 41°36'41"|E 44°33'51"||| -> will load the coordinates in the next waypoint in the sequence @|#|N 41°36'41"|E 44°33'51"|180|10| -> will load the coordinates in the next waypoint in the sequence with an offset of 180° at 10km

Then this goes back to what's already been stated a few times in the last week or so. The core missile code has been having issues since 2.9.15 or somewhere in there. 2.9.14 seems to work pretty well. All of the added missiles use the core missile code which we do not have access to and cannot influence for good or bad.

£1 paid October 2024 Deposit paid December 2024 Tonight I watched the super ultrawide angle being showcased Two more weeks and I'm pulling out.....

I tested for a while and the "loft_factor" doesn't actually seem to be what's causing the missiles to miss according to what I'm observing. It looks like it's more because the missile doesn't go "pitbull" or track when approaching the target. Here's what I've observed: it misses by maybe a few hundred feet when coming down from the loft, then it attempts to loop back to the target. (It goes pitbull after passing the target I'm assuming.) Btw, changing the "loft_factor" didn't seem to change the behavior of the loft.

Pretty much this. These last few patches introduced the first framerate/frametime problems I experienced in a long time, so at first I blamed windows update, but no other games has any issues so it definitely is caused by ED. I tried a whole list of different settings but nothing changes the headache-inducing stuttering. The only thing we can do is hope for a hotfix soon...

ждем как в Матрице, разьем на затылке

i would likely go the 24gb of vram , if you want to increase the speed of your ram fine, but you dont need 128Gb for DCS ... bear in mind that some benchmark sites have a terrible tendency to bias

Build a FF module has your problems, remember Octopus-G delayed the La-7 but need redome and remade part of your module to polish them. The Marianas WW2 map has nothing to do with the M3 F-4U and M3 PTO assets pack, on fact, I think ED has waiting to release Marianas WW2 (free), with the ED PTO assets pack. The shame situation with the F6F, ED can release them as a alone module with any map or assets pack.

Suche ein Kabel für eine Warthog/Virpil Verlängerung. Sehr kurz, bitte und nur das Kabel.

I will run tests on ohter airfields. I know you made all what you can, maybe it's the Mig 21 who has some issues. For the L-39, indeed it works, but as told while landing on runway 07 (79° bearing), the localiser was offset with the runway while using the channel 32. Seemed that it was using the RSBN as loc. For the question to @MAESTR0, I've posted a Beacons file, where the informations are completed, and several ILS updates where made. Only issue I had was on Frankfurt where the ILS on runway 07L-25R, I even tested it with the original file, with the same issue. Maybe you can test it, if you have the original file to confirm the bug. I made a video from the behavior. And if you want, you can load the Beacons file there, I just updated it with channel 32 for Damgarten.

Your limited resourses about? AI assets packs has builded by diferent teams (AI assets teams), and has none to do with a FF module develop team.

All need aproval by ED before add them to DCS World, the 3rd parties has none control on the Integration side on any update.

Lack of target distance information is odd, it should be first info that pilot get after target detection, long before identification

С какой бы радости? Очевидно к физическим ограничениям кремния подошли уже очень близко. Теоретическая 6090 должна дать прирост относительно 5090 еще меньше, чем 5090 дала относительно 4090. Цена же наоборот, по тем же законам, должна расти подобным образом - получаешь все меньше, платишь все больше. Рынок VR оказался маловат для прогресса в разработках и конкуренции. Нас с нашими ПК и симуляторами просто по касательной зацепило то, что было интересно большим дядям с их VR-AR проектами. Похоже они в этих проектах несколько разочаровались и дальше это будет такая же вялая история, как с игровыми контроллерами для авиасимов. Нишево, дорого, с кучей нерешаемых проблем.

Okay, my system is struggling with some games, including DCS, but not others. So a couple questions if I may... - Here's my system in a nutshell: Ryzen 5 5900X @ 4.4ghz 64gb DDR4 @ 3200hz RTX3060ti 8gb GDDR5 Rosewil 1K Power Supply OS and all high end games on SSD's I'm thinking the choke point in this system is the RTX3060ti with its 8gb of GDDR5. Two reasons I think this. First, when I upgraded to the Ryzen 5, I ran a bunch of benchmarks before and after to see where I was at. Obviously there was a significant increase from the old CPU to the Ryzen. At first I had the Ryzen at 4ghz on the CPU. So I recorded those and then set the CPU to 4.4ghz like it is now. Virtually no performance increase in any game benchmark. I would think if the CPU was the choke point, there would have been at least a modest performance increase from 4ghz to 4.4ghz. Second, on certain games where my system struggles, I often get a warning about my GPU running out of memory. Kinda weird but I can run a fairly new game like MSFS2024 at reasonable fps on fairly high graphics settings. But when I try to run an older flight sim like P3D V5 (it has VRS Tacpack, so I keep it around) it really struggles like, single digit fps. I recently installed P3D V6 cuz it uses a different engine than the older versions. It runs smoother, but I get the GPU memory warring all the time. So what you guys think? Am I correct? Is my GPU the choke point in my system? Which brings me to my second question. In looking to upgrade said GPU, I'm kinda looking at two new units... an RTX5070ti and an RX 7900 XT/X. On the benchmark site I go to, it shows the 5070ti in the top ten, It shows the RX 7900 XTX a bit lower and the 7900 XT a bit lower than that in the list. But obviously all of them are significantly higher than my poor little 3060ti (It wasn't bad in it's day. A lot of bang for the buck). There are of course, half a dozen or so GPU's that are better than the 5070ti, but I can't afford $2-3,000 for a GPU. A 5070ti is around $8-900 and an RX 7900 XTX is around the same price. The 7900 XT is about $100 less. The 5070ti has the mandatory 16gb of GDDR7. The 7900 XT and XTX have 20 and 24gb of GDDR6 respectively. I have used nVidia GPU's exclusively for years and have always had good performance... at the time I installed it anyway. But I have heard that the drivers for the 5070ti have compatibility issues at times, so that makes me hesitant. Also, I really like the 20 or 24gb of GDDR on the Radeon cards. Even if it is "6" instead of "7". So, what you guys think on this one? 5070ti/16gb GDDR7 or RX7900 XTX/24gb GDDR6? I will also be upgrading my motherboard and RAM soon as well, mostly because I need more SATA ports. I will go from 64gb limited to 3200hz to 128gb at 4000hz +. Unfortunately a CPU upgrade isn't in the budget just yet so I am stuck with the DDR4 cuz that's the only thing Ryzen 9 will use. So, is my GPU the choke point? RTX 5070ti or RX 7900 XTX?

Mig-21 RSBN (rotating radio beacon, a rangefinder) and PRMG (landing system) are both on channel 32. This is specificed in R_NAV_data_GermanyCW.lua file. You say when putting RSBN Mode Selector switch to Landing mode, it doesn't work? It should, there is nothing more I can do. Its all there in that file. L-39 is based on beacon.lua file, which you have already modified and tuned it to channel 32 and you said it works. But as @Tarres said there is a bug in the beacons.lua file. @MAESTR0 can you please check it out? And can you guys add airports names into quotation marks of "display name", they are mostly empty now (1st line of code): display_name = _(''); beaconId = 'airfield84_1'; type = BEACON_TYPE_RSBN; callsign = 'PM'; frequency = 820000000.000000; channel = 20; position = { -101589.343750, 52.000052, -576051.812500 }; direction = 0.000000; positionGeo = { latitude = 53.432656, longitude = 11.784527 }; sceneObjects = {'t:-1113250655'};

New to VD: with the link, I played PD 1.5, now I set godlike and PD 1.0 but the res is not the godlike one, but just the one of PD 1.0. Maybe I'm wrong with setting? Thanks for help.

I sure will! As others said, very generous. Thank you! (and great to meet another DCS enthusiast )

Well, I hope they release both of them at about the same time now, but that's only really up the them, so I just hope .

120 euro ca

That's superb thanks! I will give that a go.

What am I doing wrong.? Truman.miz

Hey pilots, can u confirm that Virtual Desktop works better than cablelink ? Isn't it weird ? I've read that this is a codec thing.

Just to be sure. Can you try with my options.lua without changong any settings in dcs ?