dorianR666

you forgot to set trim probably.

it isnt a big deal on SLAM because its videofeed becomes unusably noisy beyond like 30nm.

yep

if it is a carrier, keep clicking on the icon until the carrier is selected. then move it, planes on it will move with it. if it is a vehicle group, move the first vehicle of the group. that moves the entire group. if it is a heli/plane flight, move any. they always stick together. in other cases you cant. the editor seems bad at first, but you get used to the quirks and become reasonably efficient.

couple years later, still present

still present in current OB...

why isnt it possible to create markpoints using radar? it can already make designations for CCRP, so why not markpoints?

+1 bump its been a whole year now.

+1

Hi, how do I manually lase? Switching AUTO to MAN on the WMD7 page does nothing, neither does pressing the trigger.

According to the newsletter from last Friday, ED is working on an improved ATC for the airfields (like the ATC of the supercarrier) but there is still no ETA they said that in the 2016 new year newsletter as well (along other same items as the 2021 one, like new FLIR system) https://www.digitalcombatsimulator.com/en/news/2016-01-29_DCS_World_Future/ the roadmaps tend to be extremely optimistic.

i confirm this its like there is a hole

Because it is mandatory. It saves time of both ED and the person reporting it.

most bizarre

i hoped this would be fixed, so i could finally buy the module during winter sales. shame. its been two years now.

sounds very useful is this planned to be simulated?

i dont know about that, but you can override the need for LA with LAlt-W i believe. try that.

pretty sure its not simulated in DCS. only iff off and iff on.

i get flashes without clouds too, so that cant be it amd rx 580, latest drivers

yeah mavericks with TGP are kind of useless against moving targets. what you can do is to designate an offset on the target on FLIR page and quickly change SOI to MAVF.

multiplayer in DCS seems to be a bit of an afterthought. bad sync, no mission planner, some triggers not working for clients (scenery remove), fc3 planes not receiving datalink contacts from other clients, jtac task not being able to handle two clients in one flight, and so on. but it used to be worse in the past.

There are two separate issues here: 1) The track file only records inputs, the rest is independently resimulated. So as time goes on, the imprecision increases. This isnt really a bug, just a tradeoff. Recording changes of all states of all objects several times a second would be problematic and track files huge. If it worked this way, someone else would complain about 2GB files. 2) There is a bug that some inputs sometimes arent recorded into the track file. Its annoying but it happens quite rarely. Not as big issue as it sounds. (Though yes, it needs to be fixed). Many new players dont know about this: there is a free app called tacview, which allows you to record and analyze your flights in DCS. You dont see the ingame graphics, but it gets the job done.

Its not a problem in certain other sims/games, so my original statement stands i suppose. Consequences of ED's decisions.

What do you mean by "scene capture"? Dont you mean a separate rendertarget (= render to texture)? I dont see how that changes anything. The LODs are already in memory. They switch as you zoom in and zoom out your view for example.

there is no technical reason why TGP rendering should have the same distance limits and LODs as main view. unless DCS codebase is an even worse mountain of spaghetti than is generally known.