Asto

It seems to work with a changed shortcut. Start the DCS.exe with the params --server and new: --norender Edit: too late

Same with our Servers. Tried a slow repair, still the same as noted above Did you copy the bin to bin-mt?

When flying the F/A-18 the ATCs don't respond. I get the Cairo International airport to answer, but not the other airports. Only if I disable Easy Comms and enter other frequencies as shown in the Easy Comms mode. Example with Easy Comms enabled: Mission: Instant Action -> F/A-18 -> Sinai -> Free Flight -> Sead If I'm going to contact Al Salihiyah, it shows the Frequency 251.20 in the menu, but sets 39.60, does the callout but I don't receive any answer. Afterwards it shows and sets 39.60 in the menu but still no answers. Example with Easy Comms disabled: Same Mission: Instant Action -> F/A-18 -> Sinai -> Free Flight -> Sead If I'm going to contact Al Salihiyah manually by 39.60 -> no answer Trying 251.20 manually -> no answer Trying 119.00 manually -> I get an answer \o/ f18-sinai-atc-problems.trk

Yep same for our servers Edit: The first one got the chance to connect and is live again. Edit2: Now the second one too. I guess there is a bottleneck at the login and download servers right now

Still crashed two times, on the third try it's running again. Let's see how long. Thank you

Hey everyone, with the newest Version we cannot load Caucasus maps anymore. We've already deleted the terrains/Caucasus Folder and did a Repair and tried another Caucasus mission. The message stays the same.

Hey everyone, I'm interested in some serious feedback for my "cinematics", I've created a while ago. I find it kind of difficult to get nice scenes out of DCS but it's such a pretty and challenging game, I would love to make more movies out of it. What could I improve, what do you like? A-10C (a little bit "lengthy") AH-64D Thank you in advance!

The unit list spawns on the left position, where the UI as CPG spawns, as far as I remember. That's why it shouldn't be visible too. I've calculated the following values for your layout with the current code: Offsets: X(-1.562500), Y(0.437500), Padding: 0.711111, Compass: (-4.406944, 0.586111), Weapons: (1.281944, 0.586111) Since your x-axis reaches from -3.56 to +3.56, the compass is far too left. I don't have a fix for the formula for now, since it currently works for most users, but you could tweak your values as a workaround like this: compass_pos = { -3.0 , -0.5 } weap_control_pos = { 0.0 , -0.5 } I guess the problem is calculating everything based on the aspect-ratio and yours is very big for that screen height (ultra ultra wide layout), but that's how it works in DCS for now. I don't have the time to play with the formula right now, but I hope ED has some full time devs looking into it I would prefer the additional option to position those elements on our self via monitors layout lua file, as proposed here: https://forum.dcs.world/topic/295236-george-interface-with-3-monitors/?do=findComment&comment=4936161 (April 2nd)

@Wawar your settings don't look too bad either. The only thing I can see is that your aspect ratio in the DCS options could be a little bit off. It should be the same as your center view, so "3.55555556", not the ratio from the total resolution. But that wouldn't make a big difference. I'm wondering which offset is off. Could you try the following? weap_control_pos = { math.min(total_aspect, aspect) + offsetX - padding, 0 } The weapon control should be visible in the center on the y axis. If it's still hidden, try the other way around weap_control_pos = { 0, -1 + offsetY * 2 + padding } And the x axis should be in the center of your monitors (total resolution). By using {0, 0} it should be in the center of the total resolution. You could play with those numbers and place the UI on your own. The y-axis is from 1 to -1 and the x-axis from -aspect_ratio to +aspect_ratio

Yeah but it's still the old code, not the newest one. They didn't update it in the last hotfix

Good to hear

Looks good, but it has to move when editing those values. Are both instruments still at the same position the entire time? I've noted I have the following lines at the end of my monitor setup file. You are missing the last one, but that should change anything, hmm UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center

Weird. But well, I guess ED has to find a proper solution. Maybe letting us define the location like proposed here You should be able to create a workaround. In the line weap_control_pos = { math.min(total_aspect, aspect) + offsetX - padding, -1 + offsetY * 2 + padding } change the expression "math.min(total_aspect, aspect) + offsetX - padding" to another value. 0 should place the right element in the middle of your screens. Try -0.5 or sth. else weap_control_pos = { -0.5, -1 + offsetY * 2 + padding }

I see. But what do you mean with "latest patch"? The official DCS patch or my updated code posted here?

I've looked into this a bit more but can't find a universal solution. My last fix should work for most setups with a similar screen besides or below the main screen (note it's not in the last patch, you have to update the code on your own). But all other more complex layouts need another solution. I've thought of adding a possibility to the monitor setup lua file to overwrite the position of the George AI compass and weapon controls, but couldn't get it working. Something like GEORGE_AI_COMPASS = { xOffset = -0.82; yOffset = -0.7; }; GEORGE_AI_WEAPON_CONTROL = { xOffset = 0.85; yOffset = -0.75; } So people using a monitor setup file could place it where they want, if the default (my newest solution) doesn't work. Maybe this is even a solution for the VR users that aren't happy with their default location of the elements. Seems to be the best compromise for everyone. What are your thoughts on this? @MatveyTsivinyuk @BIGNEWY The best solution would be, in my opinion, and maybe additionally, placing those elements based on the center of the main / center view and not of the total view, as I've stated before. But I can't find that code, maybe it's inside the engine itself. (And the same for the Petrovich UI, I don't own that module, so I can't test that)