BS_Fighter

How can I remove/disable the collision of a new 3D model (static) so that it passes close from AI. "User Box" dummy far below the object does not help unfortunately. AI Planes always stops near the object. Who can help to disable object collision?

Too bad so does my AN-2 does not make sense.

Ich möchte mich an dieser Stelle unbedingt bei Dir für die tollen DCS Tuts bedanken. Sie machen einem den Einstieg in die DCS-Welt wirklich um einiges leichter :thumbup:. Weiter so...

Yes, exactly what I mean. But I've read above, it is not yet feasible for external sounds, right?

I have a new AN-2 model (initially as AI) created and integrated through the mod folder. All good so far. How can I assign this machine your own sounds (Engine...) as was done for example with the sound folders of the FW-190D9 or UH-1h? Thx

Yes, same problem without AA/AF.

I think the description was a little incomprehensible. I once made ​​a short video with the display problems of birds. Maybe someone can help...

I'm working on animated flocks of birds. These are selectable via the ME and everything is so that ok in the Sim. But I have the problem that the birds will be hidden from certain viewangles to these objects in the simulation. What could be wrong here?

I tested it with my own animated models (Animation works in Modelviewer). The ME trigger condition has been created correctly. Unfortunately, the animation is not started in the sim.

+1 The best solution!

Same question here. Who can help?

Is there a way, to connect some ambient soundfiles to the DCS-World Scenery (occupational noise on the bases...)? Is there a possibility in connection with new static edm models?

How do I remove the collision of a new 3D model so that it passes close from AI. "User Box" dummy far below the object does not help unfortunately. Ai always stops near the object. Who can help?

Pribory-09-27.tga.dds also missing in the CockpitsHDTextures.zip for the Su-25T Cockpit Seat!

Then explain it here. I add it also in the config. But the Su25T then still not responding to "iCommandWheelBrake" Command.

no axis for toe brakes Why it was not changed in FC3? A major weakness.

On such a track to compare fps i would be interested. Is there something here in the forum for 1.2.1?

Sorry Wags, but to have to completely give up AF on High End Hardware to achieve visual quality at tolerable frame rates (without stutters) can not be the solution. My Opinion...

All patches do not help me so far in terms of performance! The engine runs despite i7@4,8Ghz and GTX680 4G still just cruel with AF+AA! Still a huge difference to the version 1.2.0. There's something going wrong.

Just like here - unflyable.

Look to the texture details in the "Bazar/Textures/uh-1.zip" and in the ContainerTable.sht (M6_2xM60C and M134) ;). Understood?

Absolutely no positive change after this update! Now is also the loading time extended enormously despite Vertex3 SSD. After the start, it's a long time at 4fps (GTX680 4GB, i7@4,8Ghz)??? Damn what the hell?

To fly with 5fps in the 1.2.1 Version? :megalol:

Nice try Mustang. Unfortunately still absolutely unplayable with previous 1.2.0 settings on 4,8Ghz i7/16GB Ram + GTX680 4GB :(.

From ContainerTable.sht: --M6_2xM60C { file = "AB-212_m60"; life = 60; load = { false, false}; fire = { 0, 1}; username = "AB-212_m60"; index = 161; }, --M134 { file = "AB-212_m134"; life = 60; load = { false, false}; fire = { 0, 1}; username = "AB-212_m134"; index = 162; M134 Minigun and two M60 guns :music_whistling: UH-1H?