![]() |
|
|
|
#1
|
||||
|
||||
|
Quote:
Aviar
__________________
Intel i7-4790 4-Core @3.60GHz Asus Z97-C Motherboard 16GB DDR-3 1600 SDRAM @800 MHz NVIDIA GTX 760 - 2GB Creative SB ZX SBX Logitech X-530 5.1 Speakers 27" AOC LED - 2752 Logitech G15 Gaming Keyboard CH FighterStick-Pro Throttle-Pro Pedals Logitech G13 Gameboard GoFlight GF-T8 Module WIN 8.1 |
|
#2
|
|||
|
|||
|
Not sure whether this has been mentioned (too lazy to read a 1000 posts
Offline play: I notice that on all Ace settings 4vs4, when getting onto any AI opponents tail, it's supporting number will be onto me if I don't hit my target on the first pass. At the same time I ask my #2 to cover me.. he's nowhere to be seen ??, even after minutes of dodging the covering opponent. Summary: Target AI are able to work as a team more than your own AI = No good This is not random, but every quick mission set.
__________________
|
|
#3
|
|||
|
|||
|
Agree about Ai, sits in your blind spot and does nothing to help not even give a warning. If you're head of four, if you don't order them to do something they just follow you around, even if six enemy ai are shooting at you, lol!
|
|
#4
|
||||||
|
||||||
|
Quote:
Quote:
Quote:
Quote:
So if you have a mission where AI decided to look at the area where your plane is they will do it every time you play that mission. For breaking the randoms quickly it's best to fire short burst with your guns. Quote:
Quote:
FC
__________________
|
|
#5
|
|||
|
|||
|
Quote:
|
|
#6
|
|||
|
|||
|
FC, sorry i started new company ( exactly same like that in i see this strange acting of TB3) and i think that mission was deleted ...
can give only ntrk records (((( sorry( |
|
#7
|
|||
|
|||
|
Quote:
To add to this.. On a career, I was #4 and we attacked and decimated around 6 russki bombers. On looking at the track I found 2 yak escorts about 1000 feet above the bombers, that just went around in circles while we had 'lunch'. Sorry have no tracks or saved stuff, but will save in future.
__________________
|
|
#8
|
||||
|
||||
|
Thanks for checking, fix ready for 4.12.
__________________
|
|
#9
|
|||
|
|||
|
i'm sorry if somebody already talks about it ...
i notice that TB3 no attacking ground target not by level bombing ... now they do it like Il2 ... yesterday i watch like two TB3 keep the formation goes down from 2500 meters till 200 meters and drop bombs on the car convoy ... its not logical for this monster plane ... |
|
#10
|
|||
|
|||
|
I'm going to toss this up here in this thread, even though it might be considered 1. controversial and 2. a feature request, but I personally mostly view it as "buggy".
Simply put, the AI has ESP and can detect you trying to sneak up on them, even if it's from a completely unviewable quadrant. For example, if I set up a mission in FMB. Identical aircraft, say 109E-4's, theater irrelevant but I like sands of time. I'll start the badguy on a level flight at 1000 meters flying a perfectly straight and level track at say 300 kph. I'll start myself about 2km directly behind and below by about 200 meters. Proceed to "sneak up" on the badguy as best I can, staying directly below and behind, which I know for a fact is within the blind area. With full mouse of trackir movement, visibility in my approach area does not exist. One would have to turn the aircraft several degrees on the horizontal plane to see back directly behind. No matter what, if I execute a perfect approach completely in the blind spot, the badguy will always, always "detect" me and go defensive when I'm close enough. The detection range varies by skill as far as I can determine. I view this as a bug, there is no possible way one pilot could detect another one sneaking up like that unless they did some active, conscious flight direction change in order to "clear six". One should be able to "sneak up" on another aircraft in blind spots if done correctly. Also would like to reiterate that I realize AI development is difficult, imperfect science at best with everyone pissing and moaning about his or her particular desires, complaints, etc. Also realize there are other bigger fish to fry, like tweaking the jets a bit or who the heck knows what else. Is there any way we could get something done to help address this in 4.12? |
![]() |
| Thread Tools | |
| Display Modes | |
|
|