Unit Bubble
-
AIM-54 as example, Player leaves missile bubble after launch, missile goes DOA. Think that is what we were seeing back then.
Some of that was fixed in the “other” version and I believe that was based on some RV boyz work Code wise. We just needed to adjust the Data. Then again, maybe Fred re coded to adjust to the new Bubbles that I\We imposed on the DB.
I cannot really recall the specifics ATM as I have lost that hard drive, but I do remember setting some “General” guidelines for the Entities Bubbles back then. If we would like, I will post those, I still have a paper copy.
I guess it worked for that version as I never saw\heard any complaints i.e. BETA\Public forums, then again they could not fly stable MP without Hamachi……sigh…LOL
ALSO and risking another ban, though Temp Bubbles have been there since I think RP5, maybe SP4 actually 1.08 now that I look at it. I think they are a fix for bad data code wise.
I can see in the code where we have an easier exploitation\assertion than fixing the root cause……we have to remember that Gilman and company had Xmas coming…Sales,sales,sales…LOL!!!
Soooooo…we still have Simdata…ALL THE DATA THEY COULD NOT FIX IN CODE IN TIME FOR RELEASE…Hmmphf
As well remember, those Peep’s were Paid Professionals, and Louie had a HUGE vision, called Falcon, that persist’s to this dayHave at it,
demerI don’t know, I do know I used to test weapons and always left labels on so I can find, fire ,track weapons and units .AFAIK, agm65 (mav code) and GPU the unit label would show when cursor was over and unit is far away . now what i can’t remember was it just the TGP/Mav display only and not ground radar cursor , but either way since there used in linked most always, I don’t think it mattered .
I remember doing a lot of testing with agm154? (long range cluster bomb 30-45km , in AF we had 30nm bubbles for airports and few other .
For aim54 long range 30+ , this i remember code was alters so seaker would track and hit unit Outside of bubble , even get missile warning when appropriate .BMS has 50nm so that should be lessened of an issue now unless you would fire at its max possible distance and do 180deg . -
Damn , my memory is getting bad, but I don’t think there is a weapons bubble (at least not in same way as for damage) . I think weapon bubble is only for viewing weapon in a view so it needs to be 3d , weapons view cam .
On damage both units need to be in same bubble distance (overlapping) ,launching unit and tracked unit , now for ground ,you can have temps bubbles say that work with the whole target mission . So for example attack a objective with agm154 and each ac would put down temp bubble for min or so , so all hits would get counted with proper 3d damage .
so you might have 8-12 temp bubbles which should not be issue . -
Yes there is no temp bubble for weapons, only for the weapons seekers when used while still on the pylon (Mav/HARM seeker), as I stated above.
Temp bubbles with timer is good only for relatively short range and fast/dropped weapons (e.g Mavericks and bombs). For weapons with longer range and slower speed (e.g JSOW, JSSM) using a timer is kinda limiting.
-
-
Yes there is no temp bubble for weapons, only for the weapons seekers when used while still on the pylon (Mav/HARM seeker), as I stated above.
Temp bubbles with timer is good only for relatively short range and fast/dropped weapons (e.g Mavericks and bombs). For weapons with longer range and slower speed (e.g JSOW, JSSM) using a timer is kinda limiting.
well you can code it to whatever timer you want JSOW would be fine but yes JSSM or any very long range probably not, we are limited to 70nm bubble limit now .
Another thing might be possible is use the weapons TOF timer(from weapons FM data) for bubble timer , of course all weapons data would need reviewing -
There is a better way, use the weapon pointer
-
There is a better way, use the weapon pointer
could you explain better or refresh my memory , weapons pointer was pointer to FM, right ?
-
could you explain better or refresh my memory , weapons pointer was pointer to FM, right ?
No, not FM, I speak of the missile pointer itself (the pointer that points to the missile object in the sim).
-
Don’t you mean the missile left the Player Bubble.? As all weapons have bubble data set to 10nm & the Aim-54 has a seeker range of a tad over 11nm.
Well yes and no. The missile left the player Bubble but has not intersected the Target bubble, two separate Entities at this point…sooo…DOA,maybe the Temp bubbles will accommodate this?
In 107 even a 120 would track a target 40nm out even if you turned out early, so cant really consider that a a viable test. 108i2 was the same take the shot as soon as it shows and it will track. SP4 no different.
The 120’s are BVR weapons, as such there was a lot of attention in the code to them. Also, they have Hard coded parents, unlike the AIM154. See???
As I can’t get 102 to run, 106 has temp bubble for the mav but not for dumb weapons while 107 introduced the the radar curser bubble for non “TV” ground weapons.which remained up to SP4 but was lost by OF4.5
.I-Hawk??? IIRCC the cursor fix was for the JDAMS and their TGP.
What is the “root cause” or even better what is the “problem” ?
As to what IS the root cause\problem……Bad Data.
Many of the weapons now carried in Sim were added as model’s and appended to the DB without a thought of completing their Data correctly.
Add Copy, Add Copy…ad infinitum…heavy sigh
As far as the Boobles, my scratch pad sez I\we set them by Class data. Min|Max decided on that. Avoided the Managers and Abstract entities.
(You have to do them one at a time, Note to me…LOL)
I do believe we tried it by file type, but that gave us erratic results. Again bad data problem.
Initially set Min\Max to 50\150, think we changed some once the data was corrected.
Hope this helps,
demer -
Thanks for the reply.