Nickentik

If you use the target software i finally found an easy fix for this problem that can be used in all modules that employ a slew of some kind : find the "zoom" value for an axis and turn it negative for a slower slew.

Hello Hollywood, edit : i followed your advice and now vaicom communicates with DCS World 1.5 and 2.2, which is already a huge improvement. Thanks for that. I still have a couple of problems however : -I can only get Vaicom to work if I start a new voiceattack session every time i start a new mission. -I have tested all modules except for the harrier and a couple of WW2 craft. The following modules do not communicate with Vaicom no matter what i try : KA-50 , P-51D, TF-51D regards

I found a way to do it in the A10-A : if you target something with the dashed circle in CCRP bombing mode you can issue the command ! Kinda counter intuitive as it doesn't work with the maverick. I have not found a way to replicate this in the SU25 however...

I found a way to do it in the A10-A : if you target something with the dashed circle in CCRP bombing mode you can issue the command ! Kinda counter intuitive as it doesn't work with the maverick. I have not found a way to replicate this in the SU25 however...

No one have this problem ? :(

I'v put this topic in the dcs world bug page before with no result but i'm reposting it here as it seems more proper and with a higher chance of response. the A-10A and SU-25 have a peculiar proplem on my system : the "attack my target command" is not working. It is not even spoken, seems disabled. Al other planes, as far as I know, do not have this problem. This includes the SU-25T. No "attack my target" makes the campaings impossible as the other commands are to general. The AI is too stupid and suicidal when interpreting the "attack ground" and "attack air defenses" commands. Is anyone else experiencing this problem ? It seems quite severe to be so obscure, noone else is talking about it. It certainly is not getting recognized by support.

And another update : as of version 1.2.12 still not fixed. I did a full reinstall. curiously the su-25t does not have this problem. I can say the actual command with a target in the shkval and the wingman responds. With the A10A my pilot does not even say the command. Without wingman targeting i cannot finish any of the FC3 campaigns.

As of today it is still not fixed :(. Are we the only ones suffering from this crippling bug ? Should i do a full reinstall ?

I will not be buying the Sabre or any future belsimtek product untill these products have a manual. I feel this is the only way to force these guys to finish it.

Any news on that manual ?

Hello Belsimtek. I bought your MI8 sim a year ago and its an impressive piece of work. the lack of a proper manual makes it very hard for me to enjoy it however. I will no longer buy any more belsimtek products as long as a manual is not provided.

This is still not fixed as of 1.2.9 . Can people that DON'T have this problem reply aswell ? I'm a bit baffled this problem isn't spoken off more as it seems kinda serious. is there something wrong with my install ?

I didn't really get a satisfying reply in the DCS bugs thread about this one. It seems a rather severe bug for it to be so unknown/ignored. Is ED aware of this ? will it be fixed ? Can i do something myself ? is it an error in my install ? Got the same problem with the SU-25. Its probably all the FC3 aircraft that got this thing.

So I assume this is a bug ? Is ED aware of it ? are there plans to fix it ? If so I'l just put this campaign on hold. The only thing that works with the wingmen now is "attack ground". The wingman turns this in "attack AA" which would be fine if he hit the IR missile trucks right in front of him. However he goes for the S11 missile site 15 miles north and gets promptly shot apart. edit: su25 is not working either. Certainly this is a serious bug right ? wingmen are completely useless now

I remember it being possible with the ka50 schkval. But that was way back when Black Shark was still standalone. I'm starting from zero after a couple of years so thats why i'm now doing the flaming cliffs stuff first :p

Fair enough. Thanks for checking it out and the advice. Now I know its not an error with my install.

So there is no way for me to sent my wingman after specific targets in the A10 campaign ? That sucks a little :(

I have a problem with the a10 wingman ai (a10a Flaming cliffs): they don't attack my target when ordered to. infact my pilot doesn't even say the command. In instand action i target one of the hostiles with a MAV and order the wingman to attack my target. Nothing. Then i give an attack ground order and he immediatly begins to spam missiles. Do i miss anything here ? Its not working in the campaing games either

I have a problem with the a10 wingman ai : they don't attack my target when ordered to. infact my pilot doesn't even say the command. In instand action i target one of the hostiles with a MAV and order the wingman to attack my target. Nothing. Then i give an attack ground order and he immediatly begins to spam missiles. Do i miss anything here ? Its not working in the campaing games either

Hi, I don't know if this issue was resolved after i posted my original message but i managed to fix my issue : some of the cockpit textures are very detailed and some of them are really blurry when textures are set to High. This with an ATI HD5830 card. => fixed it by setting the mipmap detail slider in the CCC to high. It was set to performance and thats what caused it. Some ppl on simHQ had the same issue.

Is it due to it being a beta that parts of the cockpit are very low textured ? I have a good vid card (HD5830) and all the settings are at high. Parts of the cockpit (front dash and control display unit amongst others) are very detailed. The radio's on the left console however are very badly textured no matter my display settings. The caution lights on the right panel are so bad i can't even read the cautions they display.

you can clearly see the transparant building in you first picture at the top. I guess Vehicles that are labeled as structures (like the ones on the shooting range mission) suffer from the same effect. The following treat actually offers a solution regarding the fogparam values but it doesn't seem to work at all : http://forums.eagle.ru/showthread.php?t=57900

Hello, I'm suffereing from horrible transparancy when looking at buildings through the Shkval. Everything beyond 5 km is a horrible transparant mess. Is there any fix for this ? I'v tried changing the fogparam values in both the graphics and graphics_bs files but they do not change anything. This is for singleplayer missions btw.

I tried changing the FogParam2 value for Black Shark but whatever i do the buildings are still a transparant mess when seen through the Shkval. Could anything else cause this ?

after i repaired my TU25 my laser failed to activate for the remainder of the missions. Is this a known bug ?