Can I create a profile for each pylon? (to use two differents laser codes)

[maciusx]

Hi!!

 

I have loaded in the a10c this weapons

 

pylon 4: 3xgbu12, laser code 1644 (for ground JTAC)

pylon 8: 3xgbu12, laser code 1688

 

And i would like to create two profiles:

 

profile 1 to use my own laser 1688: Auto lasing, minimum altitude 1000, laser time 8 sec, etc

profile 2,to use with jtac: Default settings, autolase off, etc

 

Its is possible to assign profile 1 to pylon 8, and profile 2 to pylon 4, and cycle between each pylon each time with dms right, left? Because the thing is, creating this two profiles is easy, but when i want to cycle between profiles, it cyles between two pylons each time for each profile. Each time i press cycle:

 

profile 1 (pylon 4)

profile 1 (pylon 8 )

profile 2 (pylon 4)

profile 2 (pylon 8 )

 

And i would like to cycle like this:

 

profile 1 (pylon 8 )

profile 2 (pylon 4)

 

It is possible? I know i can deactivate profile 1 if am bombing with JTAC, but the pylon 8 remains active, and im only using the 4 for jtac, and adds extra work on the OBS. The idea is to cycle between pylons only. Assign profiles for individual pylons, and get rid of the "laser mismatch" warning each time i cycle through the pylon 4 with the "autolase on" profile 1

 

thanks

[Yurgon]

Its is possible to assign profile 1 to pylon 8, and profile 2 to pylon 4, and cycle between each pylon each time with dms right, left?

 

That's a great question!

 

Not that I'm aware of, because these are weapon profiles, not pylon profiles, and since the weapons on the different pylons are the same (despite their different laser codes), I don't know of any way to tie a weapon profile to a specific pylon. But it would be quite intriguing if this was possible, so maybe there is a way I just don't know yet. Let's keep the fingers crossed. ;)

[maciusx]

Thanks for the response

 

After some testing, I think the better “solution” it’s to create one profile , the one more complex for own purpose, for example GBU12/AL (auto lasing) and vía hud or with the rocker select it for own laser employment, making sure that the one we are going to drop it’s in the correct pylon ( in my case pylon 8 ). This way we avoid unnecesary cycles through too much profiles and pylons. If we want to use the one in the pylon 4, for jtac laser code, simply select it via click on the osb in the dsms page. This way the pylon it’s selected with the default settings (we want autolase off) and when bombing check in the hud M/GBU (manual).

 

this way we declutter some unnecesary cycles between profiles, but the downside it’s we are utilizing default bomb settings for the pylon 4. I know you can simply ignore the “mismatch laser code” warning and the “tgp laser fail” if we drope the jtac bomb using own profiles. It’s going to hit, but I like to avoid those messages.

 

Greetings

[Ziptie]

Thanks for the response

 

After some testing, I think the better “solution” it’s to create one profile , the one more complex for own purpose, for example GBU12/AL (auto lasing) and vía hud or with the rocker select it for own laser employment, making sure that the one we are going to drop it’s in the correct pylon ( in my case pylon 8 ). This way we avoid unnecesary cycles through too much profiles and pylons. If we want to use the one in the pylon 4, for jtac laser code, simply select it via click on the osb in the dsms page. This way the pylon it’s selected with the default settings (we want autolase off) and when bombing check in the hud M/GBU (manual).

 

this way we declutter some unnecesary cycles between profiles, but the downside it’s we are utilizing default bomb settings for the pylon 4. I know you can simply ignore the “mismatch laser code” warning and the “tgp laser fail” if we drope the jtac bomb. It’s going to hit, but I like to avoid those messages.

 

Greetings

 

When I plan on employing GBU-12's with a mix of buddy lase and self lase - I do what you outlined in the original post, however I never take a TER.

 

Typically will only take 3, but sometimes will load up 4 ( station 4,5,7,8 ) - will have two different codes across the four stations. I used to use auto lase and LS time a few years ago - but lately I don't do this, instead choosing to manually lase. I find that it a bit more satisfying and feel it keeps me from becoming complacent after releasing the weapon.

 

In regards to the multiple profiles, I feel like this is something that you can do but am not 100% certain. Certainly worth testing, and will hopefully get another chance to fly virtually this coming Saturday. This also allows for selecting CCRP and GBU-12 via master mode on HOTAS with HUD SOI, then simply deselecting the station that doesn't match the code I am employing on (JTAC or self lase), alleviating any auto lase fail message and allowing for various altitude drop points.

 

That being said, I agree with you in regards to being cumbersome when selecting the variation of profile via the DSMS and not sure how you would be able to differentiate the two profiles if you were cycling through via master mode select on the HOTAS with HUD SOI.

 

Certainly a worthy question you've posed, been flying the A10C for years now and a rare time when a question is asked that I cannot speak with certainty of an answer. :book:

 

 

Cheers,

 

Ziptie

[maciusx]

 

When I plan on employing GBU-12's with a mix of buddy lase and self lase - I do what you outlined in the original post, however I never take a TER.

 

Typically will only take 3, but sometimes will load up 4 ( station 4,5,7,8 ) - will have two different codes across the four stations. I used to use auto lase and LS time a few years ago - but lately I don't do this, instead choosing to manually lase. I find that it a bit more satisfying and feel it keeps me from becoming complacent after releasing the weapon.

 

In regards to the multiple profiles, I feel like this is something that you can do but am not 100% certain. Certainly worth testing, and will hopefully get another chance to fly virtually this coming Saturday. This also allows for selecting CCRP and GBU-12 via master mode on HOTAS with HUD SOI, then simply deselecting the station that doesn't match the code I am employing on (JTAC or self lase), alleviating any auto lase fail message and allowing for various altitude drop points.

 

That being said, I agree with you in regards to being cumbersome when selecting the variation of profile via the DSMS and not sure how you would be able to differentiate the two profiles if you were cycling through via master mode select on the HOTAS with HUD SOI.

 

Certainly a worthy question you've posed, been flying the A10C for years now and a rare time when a question is asked that I cannot speak with certainty of an answer. :book:

 

 

Cheers,

 

Ziptie

 

Yeah, maybe it’s time to get rid of being lazy and start doing manual lasing hahah. I was playing “through the inferno” and having a blast bombing defenseless tanks and trucks and creating waypoints via CDU with the jtac coordinates. So much fun! Then experimentating with different laser codes and profiles to not get my bombs crazy with two same lasers (the jtac one and my own plane) because, can I ask, what is the range of the gbu12 in one area to not get confused for another same laser code? If I’m bombing some trucks that are, let’s say, 50 meters next each other, can the laser of the jtac interfiere with mine? (Assuming I’m using the same) That’s why I was testing with profiles, different codes and such. I have the impression that if im bombing a group of vehicles with same jtac code (1688) sometimes the bomb goes to another vehicle. Or maybe it’s placebo.

 

And, it’s me or the gbu 54/38 it’s not very accurate using coordinates? I create the waypoint and making it steerpoint via coordinates of the jtac, but I’m not getting direct hits dropping them in range with ccrp. The hits it’s offset maybe 20 or more

meters. I read in the 2.5 subforum that maybe it’s a bug with calculations but Im not sure it’s me or it’s a bug. I think I’m doing well but not sure. With laser bombs I have not problems

[Ziptie]

can I ask, what is the range of the gbu12 in one area to not get confused for another same laser code? If I’m bombing some trucks that are, let’s say, 50 meters next each other, can the laser of the jtac interfiere with mine? (Assuming I’m using the same)

 

I do not know the exact range that the confliction would happen, but 50 meters would definitely have a confliction. I've dropped on a target that was 1-2nm from the JTAC lase and had my bomb go for his laser. That is why I choose to have at least two of the three GBU-12's that I typically have on the aircraft set to a different laser code. Can always switch them back in flight with the current capability of the DSMS.

 

And, it’s me or the gbu 54/38 it’s not very accurate using coordinates? I create the waypoint and making it steerpoint via coordinates of the jtac, but I’m not getting direct hits dropping them in range with ccrp. The hits it’s offset maybe 20 or more

meters. I read in the 2.5 subforum that maybe it’s a bug with calculations but Im not sure it’s me or it’s a bug. I think I’m doing well but not sure. With laser bombs I have not problems

 

I also experienced issues with the GBU-38 missing the target. Dropped from FL150, FL180, and FL200 - all three missed the target (SPI was generated from a PTRK in BHOT FLIR from 8nm). Target was in an flat, open field. I have not dropped a GBU-54 with the most current version of Open Beta (released 11/18/2020 xxxxxxxxxx949). Plan on testing that Saturday if I am able to fly virtually.

 

 

Cheers,

 

Ziptie