Mispunt

Hey Ramsay, thanks for that! It was the "Use second stick" being disabled. I reinstalled DCS and went through all special settings, spotted that checkbox. Figured I don't use a second stick for my camera so I unticked it. If you hadn't pointed this out I don't know when I would have made that link, and that would have sucked because I really like the Gazelle.

2.8 Open Beta, MP (Hoggit Persian Gulf) Cold start No mods SRS installed Cleaned and repaired installation before test Gunfighter MCG stick plus CM3 throttle, T rudder pedals Reproducable 1 Cold start M variant 2 Rearm with TOW, IR and sand filter + change livery 3 Turn on camera and operate, trying to fire at targets. Result: Camera shows erratic behavior. Does not want to rotate consistently, laser range finding seems to help get it unstuck briefly Camera does not ground track consistently and always temporarily Auto Slave does not work consistently as there is no stable ground track.

Same, consistent crashes flying online since 2.8. Seems to happen when I do stuff like zoom in and out on F10 map, switch to different plane external views. dcs.log-20221029-121500.zip

Hey all. Just to let you know, I released my Apache inspired skin pack for the US, UK, Greece and the Netherlands. Hope you like. https://www.digitalcombatsimulator.com/en/files/3325510/

Hi all, I am new to this forum and hoping someone can shed some light on this issue. I am working on a fictional skin pack in the messy style of the Apache and Chinooks. However, the SA342_Camou_ADT_7_spec map does not go from black to white, despite those values being present in the spec map. As far as I can tell all skins that come with the module, and all screenshots I see online of other skins display this same issue, just look for the darker tinted underside under the door, or in the roughness channel of the Modelviewer. I suspect this is a problem with the shader not the textures, so I won't be able to fix it. But figured it's worth a shot asking if anyone knows what's going on. I added my skin and Polychop's default skin for clarity. As you can see the bottom and cockpit struts are much lighter in the viewer and lost all contrast the textures have. Cheers, Mispunt

I found a dirty, hacky workaround, I think. Change {"F16_bl50_Main_1", ROUGHNESS_METALLIC,"F16_bl50_Main_1_RoughMet",false}; {"F16_bl50_Main_3", ROUGHNESS_METALLIC,"F16_bl50_Main_3_RoughMet",false}; to {"F16_bl50_Main_1", 2 ,"F16_bl50_Main_1_RoughMet",false}; {"F16_bl50_Main_3", 2 ,"F16_bl50_Main_3_RoughMet",false}; This will load your own map on the model again. Then invert the G channels and tweak the contrast of your RoughMet maps to make them look okay again. I'd wait for the bug fix though.

F16_bl50_Main_1_RoughMet and F16_bl50_Main_3_RoughMet seem to have their green channel values inverted on the model (white on the texture map is now black on the model). You can tell by the shiny decals on the body and the shiny grime around the gun port.

Oh you are right, it gets very close these days, I was coming from the fact that these renders use proper global illumination and this is still some time off in real time. Some of the subtleties in these shots can easily be faked (ambient occlusion specular maps, low res image based lighting and environment mapping go a long way in that respect) but it will always feel not _quite_ right.

The reason it looks so real is the lighting. Shadows, reflections and highlights of this quality are not possible yet in real time. So it's definately not a representation of "in game" quality and can in that respect be a little misleading. Still, say in 5 to 10 years we will be there. :)

Very nice model! And I didn't know ED are going for polycounts like this themselves, excellent. Now maybe you guys can start focussing on the lighting as well? Real time AO, specular and cosine maps, in cockpit self shadowing and Image based fill lighting is all I want. :D

Anything but an F15, F16 or an F18 (Though I wouldn't mind a Strike Eagle) :) Oh and a Mi-28 please :D

This would be largely an art and scripting task with a limited amount of engine code support (I reckon, but then that's within my own frame of reference). So yes. Spending time and effort on little things like this does not have to detract from the overall effort of improving AI, physics, avionics or graphics code since these are very specialised areas of expertise. There is no unified pool of resources that every feature comes out of.

Looks cool, now bring on the DCS: T-80 module. :D And no this does not detract from ED's efforts of improving the main pillars of this sim. Programmers do tech stuff, artists make the pictures prettier.

I guess I am one of those that actually don't mind unwrapping (sadly I don't really have the time to help with mods). I enjoy both modelling and texturing and the better the unwrap the more you get out of your textures. Can't stand to unwrap someone else's model though. ;)

Deployment campaign I have had a freeze today on Coday, it happened as I was touching down on the Skala FARP to re-arm. I had to quit the game module and was brought back into the interface module after that. Contents of report: # -------------- 20090104-155615 -------------- C:\Windows\system32\nvd3dum.dll # C0000005 ACCESS_VIOLATION at 14C5B369 01:0021A369 # # EAX = 00000000 # EBX = 1521F000 # ECX = 003744A8 # EDX = 0038F0C8 # ESI = 1510B240 # EDI = 51975068 # CS:EIP = 001B:14C5B369 # SS:ESP = 0023:0012FBE4 EBP = 0012FC04 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010216 And: # -------------- 20090104-155559 -------------- C:\Program Files\Eagle Dynamics\Ka-50\bin\stable\Flight.dll # C0000005 ACCESS_VIOLATION at 027F1949 01:00010949 # # EAX = 4076013F # EBX = 00000001 # ECX = BF167914 # EDX = 00000000 # ESI = BF167914 # EDI = 41695464 # CS:EIP = 001B:027F1949 # SS:ESP = 0023:0012F940 EBP = 00000003 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010202 027F1949 00000003 0001:00010949 C:\Program Files\Eagle Dynamics\Ka-50\bin\stable\Flight.dll ?isRunWayOpen@woATC@@QAE_NXZ()+9 027F1949 00000003 0001:00010949 C:\Program Files\Eagle Dynamics\Ka-50\bin\stable\Flight.dll ?isRunWayOpen@woATC@@QAE_NXZ()+9