Shadoware

I tried now and its great! Eagle Dynamic needs to make this official!

Suggestion just in case you decide to change something in the future: Could you make the grass near runway more uniform like this? When the aircraft is in the runway is the only moment we can see more unrealistic textures, but I think this happens in every game.

Im gonna use this modified terrainoptions41.lua too, thanks. What I think is strange in PG map is when we fly low, the desert texture makes hard to guess the altitude. When we fly high the map is beautiful.

If Tpod could lock on to targets provided by AWACS it would be a very stealthy way to shoot enemies!

This is the first mod I install and its the exactly the way I wanted it to be. It feels very realistic! ED should make it official! Many thanks! P.S. Mustang, if you have the time, could you make a mod to Persian Gulf too? The city is great but ground textures are not.

And how about air targets? Can Tpod be used as some kind of IRST?

Can the Tpod be slave to a target displayed in HSD data link?

It seems beautiful! Could you make a video?

From some altitude the textures should look more uniform anyway, maybe 10000 feet.

This project is awesome Barthek! DCS really needs a terrain texture overhaul! I would like to make a suggestion if possible: I was watching the below video and when the aircraft is high, the grass seem so plain and even! It would be cool if the textures looks more even when seem from high altitudes, we see some areas so evenly green! That could help us realize that we are really flying high and when we are low more details could become more visible. (Look at 3:15 ground textures)

I tested in Start up tutorial and HSI is not receiving navigation data too. In the Taxi tutorial everything is Ok. Instant action/Caucasus/cold and dark start/ I found the same problem! I think all missions with aircraft could and dark has the same problem. Was this bug already reported?

Does anyone knows these acronym meaning? Its good to know as a memorization resource!

I realize that when I star that miz file the controls are too sensible every time, ignoring the curves but after I move the stick to extreme positions DCS starts applying the curves correctly. I recorded a short trk file showing that! Control_Response.trk

I just complete my first refuel without any disconnection! Now I pay attention mainly on the tanker but I keep an eye on the TVV too because to keep my jet horizontally leveled is the harder part now. Its very hard to control the pitch to keep the jet neutral without any overreaction/underreaction and watching the TVV a bit REALLY helps this. To use a curve in the Y axis was essential too!

I think this limitation in CatII is to prevent damage to the aircraft due the high weight of AG munitions, so, limit G is more important.

I think it would make more sense to limit G and and roll rate. AOA is not so important.

I erroneous marked the post [REPORTED] - Cannot correct! Sometimes the aircraft response dont seem correct! If change from CatII to CatI and return to CatII(and vice versa) the response may return to expected. Other times I have to open control settings/axis tune and click "OK" button! I made some more tests today to confirm the bug. I was using 19 in Y axis! The response was too fast! I changed the curve to 25 and noting changed! I change again the curve to 70! There was a small change in sensitivity and suddenly the control response becomes too slow so I put 19 again the response was correctly and slow in the right amount! Sometimes DCS seems to ignore the curves and use the control stick raw data! This is an intermittent bug and really needs a fix! System: I'm using latest DCS Steam version in PG map and I use Saitek x52pro Hotas and Windows 10 pro 64-bit. I created a refueling training mission where I realize the bug more frequently. Hardware: Core i5 6600k, Rx5700 and 16Gb DDR4 3000MHz Im going to attach my settings file and the mission file. options.lua BdaPosition.lua Treino_AirRefueling.miz

Im landing very good now. Landing is always lousy at first but you will grasp it fast if you practice! The top important thing is to control you speed, this is super important and keep FPM in the runway threshold! Other most important thing is to trim the aircraft so you wont need to keep pulling the stick hard and the plane will keep the glide-slope easily! After that, when you flare(or round out) the plane, dont set your throttle idle immediately but keep in last position until the plane is leveled, then put the throttle to idle and let the plane touch down. In this video I was landing heavily loaded so my speed is high:

CONFIRMATION! There's really a bug! I made some more testes. I was using 19 in Y axis! The response was too fast! I changed the curve to 25 and noting changed! I change again the curve to 70! There was a small change in sensitivity and suddenly the control response becomes too slow so I put 19 again the response was correctly and slow in the right amount! Sometimes DCS seems to ignore the curves and use the control raw data! This is an intermittent bug and really needs a fix!

That's not the case, I have dead zones here.

La taille du texte que vous pouvez facilement modifier dans les options de configuration DCS. La position, je ne sais pas s'il y a un moyen. Translated by google.

The problem I realize is the contrary: The control acting without any attenuation despite I applied a curve set 19 in the Y axis!

Sometimes the aircraft response dont seem correct! If change from CatII to CatI and return to CatII(and vice versa) the response return to expected. Other times I have to open control settings/axis tune and click "OK" button! The FLICS change the control sensitivity depending on situations but sometimes its easy to realize the controls are not responding as usual. It seems a intermittent bug. It doesn't happen all the time. P.S. Im using latest Steam edition and Saitek x52pro Hotas. ***** The bug is confirmed! See the post below! ********

This module is early access so its not ready but why would they do that?