Jump to content

Recommended Posts

Posted

When I select default loaded clusterbomb 105 with HOF 1800,

CCRP locked at ground spot @ 9000ft

the CBU-105 will not release.

 

When I change the HOF to 700 via the inventory,

CBU-105 will release and performs as expected.

 

What am I missing?

| VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |

Posted
When I select default loaded clusterbomb 105 with HOF 1800,

CCRP locked at ground spot @ 9000ft

the CBU-105 will not release.

 

When I change the HOF to 700 via the inventory,

CBU-105 will release and performs as expected.

 

What am I missing?

 

CCRP locked at 9000ft, is that AGL or from MSL? What is your altitude from the ground?

To whom it may concern,

I am an idiot, unfortunately for the world, I have a internet connection and a fondness for beer....apologies for that.

Thank you for you patience.

 

 

Many people don't want the truth, they want constant reassurance that whatever misconception/fallacies they believe in are true..

Posted
CCRP locked at 9000ft, is that AGL or from MSL? What is your altitude from the ground?

 

9000ft is the reading from the A01 HUD (MSL i guess),

this is one of those Quickstart situations I edited to start in air 3x the distance to first target and at 9000ft - it's inland (AGL perhaps 7000ft?) I use for training CBU release

 

Now that you mention it, not in this case/example, setting (resetting?) HOF to a lower reading also gets rid of 'bad terrain read for target' or something in the HUD in other situation, cant remember which, but I think when low, when I dot Not edited start waypoint height, so like MSL 3000 in those Quikstart situation (AGL 1500ft ?), not sure if this is anywhere related.

 

It's like default CBU HOF loaded when situation starts inflight creates the error / doesnt read situation properly?

(wild guess here, or what did I miss)

| VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |

Posted

It sound a little like you do not have enought altitude above target to use HOF1800. I may very well be misinterpretting the info. If your target elevation is 9000MSL and you are flying at 11000MSL you may not have enought height over target for IFFCC to release the weapon.

That is why it will release when you lower HOF to 700.

 

As mentioned I may have misunderstood your description and if I did could you post the mission or a track?

 

Cheers

Hans

Posted

How do you change HOF? I did look at "change set" but did not see something like that

| A-10C | MiG-21bis | Hawk T1.A | L-39 Albatros | F-5E | Ka-50 | Mi-8 | NTTR | CA | SU27 | M2000C | F-86F | AV-8B | F/A-18C | Mig 15 | Mig 19|

Specs

 

Intel i7-9700k

msi GTX 2060 Gaming Z

msi Z390 Gaming PLUS

16gb RAM

Hotas Warthog

 

Posted (edited)

Go to DSMS,

press INV on OSB5

Select stations holding CBU

Press OSB3 INV STAT

Cycle through the different heights on OSB18

 

Above is slightly faster than the method described in the manual;

Go to DSMS,

press INV on OSB5

Select stations holding CBU

Press CBU OSB7

Select the correct type of CBU on next page

Cycle through the different heights on OSB18

 

Cheers

Hans

Edited by Hansolo
Posted

thank you

| A-10C | MiG-21bis | Hawk T1.A | L-39 Albatros | F-5E | Ka-50 | Mi-8 | NTTR | CA | SU27 | M2000C | F-86F | AV-8B | F/A-18C | Mig 15 | Mig 19|

Specs

 

Intel i7-9700k

msi GTX 2060 Gaming Z

msi Z390 Gaming PLUS

16gb RAM

Hotas Warthog

 

Posted
9000ft is the reading from the A01 HUD (MSL i guess),

this is one of those Quickstart situations I edited to start in air 3x the distance to first target and at 9000ft - it's inland (AGL perhaps 7000ft?) I use for training CBU release

 

Now that you mention it, not in this case/example, setting (resetting?) HOF to a lower reading also gets rid of 'bad terrain read for target' or something in the HUD in other situation, cant remember which, but I think when low, when I dot Not edited start waypoint height, so like MSL 3000 in those Quikstart situation (AGL 1500ft ?), not sure if this is anywhere related.

 

It's like default CBU HOF loaded when situation starts inflight creates the error / doesnt read situation properly?

(wild guess here, or what did I miss)

Try climbing to a higher altitude, those the problem persist from a higher altitude?

To whom it may concern,

I am an idiot, unfortunately for the world, I have a internet connection and a fondness for beer....apologies for that.

Thank you for you patience.

 

 

Many people don't want the truth, they want constant reassurance that whatever misconception/fallacies they believe in are true..

Posted
Try climbing to a higher altitude, those the problem persist from a higher altitude?

 

I've tried from a highly altitude with inconsistent results, which still seems to point to some sort of bug that pre-programs the CBU, which it shouldn't, only happens when missions starts in the air.

 

(Wild guess, anyway, Not using the default, setting the HOF makes it work)

| VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |

Posted

Do you always try in the same target area?

To whom it may concern,

I am an idiot, unfortunately for the world, I have a internet connection and a fondness for beer....apologies for that.

Thank you for you patience.

 

 

Many people don't want the truth, they want constant reassurance that whatever misconception/fallacies they believe in are true..

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...