AI's disappear when I am 60 miles away from them
-
I am sorry to use F4Browse, but - open “Unit” - “Fighter - MiG-31(Type flight)” - the only field with bubble is “CT Ind (its CT for fighter)” then “Bubble Dist” (default 303800)….607600 new value OK?
When I open MiG-31 flight in Falcon Editor, I can not see bubble value for flight
Edit: I think I found it…is it this ?:
CT 286 “Fine update range 303800.0000” -
BTW I used to know quite a lot about bubbles, but forgot many relations - so fast question
if bubble value for MiG-31 flight is changed, does it mean:- when flying MiG-31, I will deagg all flights 100nm around me regardless their bubble value…?
- Do I need to change value for all other flights (potentional targets) too…?
EDIT: ok, CT 286 (MiG-31) set to “607600”…I see packed F-15 flight labeled 115nm+ (far + short labels on), but I am able to lock on at 79-82nm distance and I can switch targets in TWS… AA-9 launched at around 65nm (it was impossible before)
EDIT2: yep, enemy flight really seems to be packed visualy in 3D, but “lockable” on radar screen and missiles are guided…when changed to missile view, F-15 flight deagregates at 50nm visualy (F-15s individual labels are clearly popping at 50nm and it is possible to switch enemy view to see them)
EDIT3: it seems this lockable (but visualy agregated) flight at 80nm is divided into individual targets on radar, but they are displayed cold, until flight deaggregated (targets turn to hot at 56 nm - still more than before).
EDIT4:
it seems only flight leader is able to lock 50nm+ with this settings! :mrgreen: -
This post is deleted! -
yes, but I was never able to lock anything above 50nm in AA before. Tweak has some effect, but needs fine-tunning.
I need also longer awacs - current one is not interested in class A fighters 80nm away.
I dont say this all is good for campaign, but I would like to have it working in TEs. Default state is better than Falcon3.0 (enemies popping 20nm away), but still not ideal. 50nm first contact appearance is big limitation in modern air combat simulation (building your possition is essential).
-
Lukas - Generally I think it’s the other way around, i.e if you change the MIG-31 bubble dist but you fly a MIG-31 all other ACs will deaggregate at their assigned distance (Because deaggregation is relative to the player position).
If you want to see the MIG-31 bubble change comes into play then you will need to fly other AC and target a MIG-31And as Mortesil said, I think (REALLY not 100% sure) that AA radar cursors has temporary bubble indeed and once you put the cursor at something, the “area” of 1NM around it will deaggregate.
A-G wise, I implemented many types of temporary bubbles in 4.33:
- A-G radar cursor have a temp bubble
- TGP cursor will have a temp bubble
- SPI (if AGR or TGP is controlling the SPI but even if something else, e.g HUD slewing) cursor will have a temp bubble
- Maverick MFD have a temp bubble
- HAD/HAS displays have temp bubble
- All A-G missiles, including ones fired by AI, will hold a temp bubble around their target area. That was made mainly to keep long range missiles like SDB/JSOW to not hit dirt due to bubble limitations
- All bombs, including ones dropped by AI will hold a temp bubble.
-
yep, you are right - I had a sucpiction it works opposite……but I did my test in Nordic (I have personal tweak with low-res textures, working very nice) and Nordic TE has too many teams (default one) and I was not able to find my F-15 :)… so I tried other side…and saw difference - caused probably by that 800 000 AII value I did not undo before…??
BTW mentioned AII file has some interresting rows!
[ATM]
….
MaxFlymissionThreat=85
MaxFlymissionHighThreat=100
MaxFlymissionNoThreat=10
MinSeadescortThreat=20
MinAvoidThreat=40
…
MinimumAWACSDistance = 110
MaximumAWACSDistance = 140
MinimumJSTARDistance = 180
MaximumJSTARDistance = 300
…I tried from other side and i see Foxhound full labels deagg 100 nm (and can use enemy wiew “6” too).
Both targets are hot on radar screen (well orientated). -
Hmm
In the past bubbles where all over the forums.
Total confusion and erratic tests.Good thing I hawk managed those changes.
They r so dynamic that I don’t believe anyone can fully master them.
Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk
-
During 4.33 Development period, I worked on many A-G systems/sensors but what got me to chase those temp bubbles was 1 simple test. I tried something with AI flights and noticed amazingly that the AI dropping bombs on anything outside the player bubble will hit nothing but dirt.
I.e think this way:
You fly to your AG target and 20NM away from you there is a 4-ship AI flight attacking some other target.
If at the moment of AI bombs reaching their target, that target is aggregated for you, the AI bombs will hit nothing and count as misses.
OTOH - If you will follow with camera the AI bombs, that camera will cause the targets to be deaggregated and bombs will hit fine.That was a shock to me to find that after all those years a huge number of AI flights in campaign wasn’t count whatsoever… hence my changes.
-
During 4.33 Development period, I worked on many A-G systems/sensors but what got me to chase those temp bubbles was 1 simple test. I tried something with AI flights and noticed amazingly that the AI dropping bombs on anything outside the player bubble will hit nothing but dirt.
I.e think this way:
You fly to your AG target and 20NM away from you there is a 4-ship AI flight attacking some other target.
If at the moment of AI bombs reaching their target, that target is aggregated for you, the AI bombs will hit nothing and count as misses.
OTOH - If you will follow with camera the AI bombs, that camera will cause the targets to be deaggregated and bombs will hit fine.That was a shock to me to find that after all those years a huge number of AI flights in campaign wasn’t count whatsoever… hence my changes.
Has this been fixed?
-
Read post #19
Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk