Snacko

If you are flying with Easy Comms OFF, What frequency/radio do you use to talk to your flight?

OpenBeta: I noticed today the most of my Huey Liveries were Missing the Textures for the external Gun Mounts. Further investigation showed that this only happens on the Custom Liveries. For some reason DCS loads the texture for the built-in skins, but not for the 'custom' skins/liveries. I tested this by copying the needed files into a custom livery that was missing the textures, and that fixed them. But this is a bug, right? I don't need to do that to all of my custom skins. These are the files: uh1_weapon.dds uh1_weapon_blk.dds

You have to rename all xxx.bmp.dds and xxx.tga.dds to just xxx.dds And remove the bmp and tga from description.Lua for those files. Sent from my Moto Z Play using Tapatalk

Yes, I just found this great tool and it worked the first time, then no more. I was probably extracting an older aircraft, but can't even do the P51 now. Arg..

Wow, I had not heard about this. I've been trying to fix several mods for 5 hours today. Now I am able to fix them. Thanks. @Fakum: Also found this.

Are they planning on fixing this??? Or should start changing all my mods? I would hate to fix everything and then have to change it all back!! :joystick::doh:

I just downloaded your Black Pit for the Huey from LockOnFilesdotcom and for some reason I get all Missing Textures. Has the description.lua changed or something? How can I fix this?

I noticed a missing FARP texture yesterday and after a redownload it fixed it. Do you have any Antivirus running? Sometimes that can 'fix' files without you knowing.

Just tried this mod and it seems to work fine except for these missing textures. The same textures are missing from both versions. I downloaded it twice, but got the same missing textures... Is there anything I can do to fix it?

I know this was a problem for many aircraft last summer. I just recently started flying the Huey again. And at night, the Position Lights and the Collision Lights show in the Interior of the aircraft. Thought this was fixed a long time ago. :joystick:

Alex posted the fix above.. Sent from my Moto Z Play using Tapatalk

Yes, that's it. You don't like bending and we don't like stretching. It didn't take long for me not to notice it.

Does this still work? I have put the Black version in the folder that I emptied here, but it doesn't show up in game. \Mods\aircraft\F-86\Cockpit\Resources\Model\Textures\F-86F-35-CPT-TEXTURES So, I tried just replacing the F-86F-35-CPT-TEXTURES.zip with my .zip of the Black files and still doesn't work. Don't these skins need a description.lua file?

I have nVidia Surround on all of the time. Most people probably use the '1 Screen' monitor option, which is a bit stretched at the edges. You just have to compare and see for yourself. If you try the 3 Screen monitor option in Settings, the game will render 3 views(not 1 stretched one). My nVidia Surround is still on, it doesn't matter I don't think. I did some tests about a year ago and here is a comparison. I can't remember exactly how many FPS this cost but I remember that I felt it was way worth it! I think it was 3-5, but that will depend on your system. When you zoom way out the view get's wrapped around. So, I have zoom mapped to a wheel on my throttle and have a curve on it to stop the zoom out at a certain point. In the second image there is a bug in the corners of the harrier which I believe has been fixed. You can see the edges of the Helmet shield. These images were resized in MS Paint, so they have some jaggies AA on straight lines. Has nothing to do with 3 Monitors.

Thank you for that.. Now I need to update again. LoL :thumbup:

I tried swapping the Left and Right viewports, but that didn't fix it. I don't understand why it didn't fix it unless their internal code is just ignoring the lua code. I tried using the 1Camera.lua and now I get a Shader error that crashes the game. Ended up Reverting back to the last update: DCS_updater.exe update 2.5.4.25729

Since this is an ongoing problem, recurring several times the past few months.. Will there be any changes to your Quality Assurance Testing Procedures to prevent this from possibly happening again in the future?

It's more than the left and right being swapped. When I turn my head I see the center cockpit panel on 2 screens! I tried editing my MonitorSetup lua to move the left to the right, and the right to the left. And it was still screwed up. It is really weird. And when I try to use the 1 camera lua, I get a Shader Error that crashes the game!!

So, with todays update, the Triple-Monitor is totally broken and unplayable. I tried to fix it using different luas, but that didn't work. It looks like the left and right monitor are swapped, but in the MonitorSetup lua I swapped the left/right sides and for some reason that didn't fix it. And it looks more like the views are way off because I see most of my cockpit on 2 monitors! So, I tried to go back and use the 1 Monitor(1camera.lua) in the stock game folder and I get this error. I cannot even load the game now. But if I edit my Options.lua and tell it to use a different monitorsetup lua file (triple screen) I do NOT get that error. So, Single-Camera is fubar, and Multi-Monitor is fubar. It's all fubar! :joystick::mad:

Thanks for that answer. Is there any documentation 'tree', or any way I could read about this lining up for the runway trick? I found out a few days ago that the reason I got no response for a Request Takeoff, was that I was not at the correct Runway apron at Nellis(2 runways). This 'trial and error' is not a good way to learn these rules. Also, any idea about my Command Delay that I posted above?

Try this: https://forums.eagle.ru/showpost.php?p=3662693&postcount=1119

And yet AGAIN, Multi-Monitor gets screwed up!! Seriously, the Triple-Screen support has been screwed up probably 4 times out of the last 10 updates. And once it took about a MONTH to get it fixed. This is getting very annoying. Can you have someone check this with every update?? I've tried two 3 Screen lua files and both do the same thing. Here's the first one: _ = function(p) return p; end; name = _('My 3 Screen'); Description = 'Configuration with 3 identical monitors each with its own camera' Viewports = { Left = { x = 0; y = 0; width = screen.width / 3; height = screen.height; viewDx = -1; -- -1 viewDy = 0; --[[viewDx & viewDy: They define the viewing angle of the image. Dx and Dy can be decimal fractions. A greater absolute value of Dx makes the image look like it's being panned more sideways. But with that value, you need to physically rotate your left and right monitors more out of alignment with the center monitor to match the visual effect in the game. If this feels unconfortable and you decide to tune the values down, you might end up with something like 0.8 or 0.9(can't remember exactly), and find out that the images on the left and right monitors partially duplicate the center image along the joining edges.--]] aspect = screen.aspect / 3; }, Center = { x = screen.width / 3; y = 0; width = screen.width / 3; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 3; }, Right = { x = screen.width * 2 / 3; y = 0; width = screen.width / 3; height = screen.height; viewDx = 1; -- 1 viewDy = 0; aspect = screen.aspect / 3; } } UIMainView = Viewports.Center --[[ also you can use "displays" table to perfectly match you configuration . it is generated by DCS automatically. displays table is contains information about all currently attached displays for example my setup is : displays = { [1] = { x = 0, -- note : x == 0 and y == 0 is always mark primary windows display y = 0, width = 1920, height = 1200 }, [2] = { x = -1440, -- mark that secondary display is on left side of primary display y = 0, width = 1440, height = 900 }, ... for all displays } screen table also contain x, y members which mark top left corner of DCS window note about fullscreen : directx doesn't allow fullscreen applications with resolutions more than primary display can handle, so multimonitor presets in DCS will fall back to windowed mode if fullscreen initialization failed ( this info also will be printed to dcs.log) for reconfigure viewports setup for each unit type independently you can declare here function function reconfigure_for_unit(unit_type) --unit type is string with unit name if unit_type == "A-10C" then Viewports = ... define new Viewports table -- also you can define cockpit displays viewports here RIGHT_MFCD = ... define new RIGHT_MFCD viewport else Viewports = ... define default for others RIGHT_MFCD = nil -- remove for others end end --]] And this one, that I called 'My 3 Screen DCS BUGGED', because it was a fix for the last time you screwed up Triple-Screen with 3 cameras. _ = function(p) return p; end; name = _('My 3 Screen DCS BUGGED'); Description = 'Configuration with 3 identical monitors each with its own camera' Viewports = { Left = { x = 0; y = 0; width = screen.width / 3; height = screen.height; viewDx = -1; -- -1 viewDy = 0; --[[viewDx & viewDy: They define the viewing angle of the image. Dx and Dy can be decimal fractions. A greater absolute value of Dx makes the image look like it's being panned more sideways. But with that value, you need to physically rotate your left and right monitors more out of alignment with the center monitor to match the visual effect in the game. If this feels unconfortable and you decide to tune the values down, you might end up with something like 0.8 or 0.9(can't remember exactly), and find out that the images on the left and right monitors partially duplicate the center image along the joining edges.--]] aspect = screen.aspect / 3; }, Center = { x = screen.width / 3; y = 0; width = screen.width / 3; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 3; }, Right = { x = screen.width * 2 / 3; y = 0; width = screen.width / 3; height = screen.height; viewDx = 1; -- 1 viewDy = 0; aspect = screen.aspect / 3; } } GUI = { x = screen.width / 3; y = 0; width = screen.width / 3; height = screen.height; } UIMainView = GUI -- UIMainView = Viewports.Center --[[ also you can use "displays" table to perfectly match you configuration . it is generated by DCS automatically. displays table is contains information about all currently attached displays for example my setup is : displays = { [1] = { x = 0, -- note : x == 0 and y == 0 is always mark primary windows display y = 0, width = 1920, height = 1200 }, [2] = { x = -1440, -- mark that secondary display is on left side of primary display y = 0, width = 1440, height = 900 }, ... for all displays } screen table also contain x, y members which mark top left corner of DCS window note about fullscreen : directx doesn't allow fullscreen applications with resolutions more than primary display can handle, so multimonitor presets in DCS will fall back to windowed mode if fullscreen initialization failed ( this info also will be printed to dcs.log) for reconfigure viewports setup for each unit type independently you can declare here function function reconfigure_for_unit(unit_type) --unit type is string with unit name if unit_type == "A-10C" then Viewports = ... define new Viewports table -- also you can define cockpit displays viewports here RIGHT_MFCD = ... define new RIGHT_MFCD viewport else Viewports = ... define default for others RIGHT_MFCD = nil -- remove for others end end --]]

Command Delay: So, I finally have VAICOM working most of the time. But I sometimes, it has a long delay(45 seconds) before it issues my spoken command. The Log window recognized the command and beeps, so I assume it is telling DCS the Radio command. But I have to wait 45+ seconds before DCS says and displays my command on the screen. Is this something I can fix? It's pretty annoying. :joystick: Missing 'Request Landing' command: Most of the time, after I have Requested Vector to the airbase, and reported Inbound, I 'Request Landing', but get NO Response. A friend told me that he has to be lined up on Final for it to work. I have done this many times and still no response. When I look in the Radio Menu, there is NEVER a Request Landing command available. Yesterday was the first time it worked! It worked only once at Creech on NTTR. I had to be lined up with the runway about 8 miles out. I was surprised that the command was issued and appeared on the screen "Indian Springs, Uzi 1-1, Request Landing", and they responded!!! So, I looked on the Radio menu for Creech ATC and there was still NO Request Landing command on the menu! Is this a bug?? How can VAICOM issue a Radio Command that doesn't exist on the menus? And why is it not there.. or what do you have to do to make it appear? :joystick:

Attached is Loz A10c profile. I had to break it into 2 uploads because the DCS forums have a 9.77mb limit per file. Just combine these two zip files and you have the entire profile. :thumbup: Snack Loz SM v2.1 - Part 1.rar Loz SM v2.1 - Part 2 (more images).rar

This is the view that I have when I lean forward and turn around. My head should be higher! :helpsmilie: