4.33 Issues (Known or not)
-
Hello i do not know if my Greeks fellows mention it or is just in my pc
When i select HAF F-16 block52+ or HAF F-16 block52+ w/CFT in a new TE Korea Theater , i create a new TE , e.g CAS save it , fly
The RWR is the USAF( Raytheon (Litton) AN/ALR-69(V) one and not the **Raytheon (Litton) AN/ALR-93(V)1
i check also the Avionics config the type is 3 # Greek type
also the fm F-16blk52+ & F-16blk52+ CFT and the type avionicsRWRType 3 #Greek version** check both into 32 and 64 bit
if i change type e.g 5 the HAF then have this RWR type 5 i check the functions it has type 5 but the BIT or launch buttons are all the time the same type 1
the same for type 3 i check the RWR functions in RWR display but not type 3 BIT or other buttons
is it possible to be only RWR texture problem?
can you help me?The RWR problem occurred only in defaults BMS 4.33 Korean theaters and Israel Theater , in Balkans the RWR in HAF models is correct Raytheon (Litton) AN/ALR-93(V)1
Can the devs reproduce this ?
kind regards
-
Ciao a tutti from Rome,
This 4.33 seems awesome, and
I’m enjoying very much trying VTOL operations with av-8b+ (in balkans)… really nice addition to “Falcon” BMS…But it seems to me that something is bad with the cockpit…*
there is an error in instruments, in the centre panel there is a compass (maybe…it’s a white-black ball, always N pointed) instead of the ADI (Attitude Direction Indicator)… in BMS document “3D cockpit Harrier” is also wrong…
Without an ADI is horrible trying to flight IFR with head down…*Other bad thing are the HSI HDG/CRS buttons; they work, but the middle mouse wheel cannot be used to get a swift set (i know a switch is not a rotary knob, but even a continuous click doesn’t work), if current heading is 360 and you have to set at 90°, it should be clicked 90 times! [emoji26]
Anyway, is a great start for harrier…
-
I’ve come across an issue with Kimpo RW signs. When I’m told to taxi to RW 14, all the signs point to RW 32. The EOR has a large “14” painted on it though, and also according to my heading I’ve taxied to the correct spot.
I can provide screenshots if this is of any help, and yes, I might totally be misunderstanding of the intricacies of RW signs / labelling
All the best, Uwe
-
-
I am not getting a DLZ displayed for CBU-104’s. CBU-103’s and CBU-105’s work fine.
-
Paragraph 3.4.10.1 of the game 34-1-1 states that “For WCMD in ripple release mode, the avionic system uses the attack azimuth to calculate target offsets for each weapon to achieve at the target. At release, the bombs will fly from the aircraft direct to the target and the offset sent to the weapon is corrected/adjusted for the Attack Azimuth input”. What exactly does “corrected/adjusted for the Attack Azimuth” mean? Can someone provide an example? The situation to me is quite confusing since sometimes when rippling WCMDs with an attack azimuth, the bombs will fly straight without any discernible attempt of making the set azimuth, sometimes they fly the usual “curve”. PRE mode set in all cases, and pickling within LAR2.
-
-
Don’t know if bug or feature. The speedbrake indicator in the cockpit jumps from fully closed to fully open, it doesn’t “roll” in sync with the physical brakes anymore. Anyone else seeing this?
-
normal behavior
-
Yep, the missile rail launch is not optimal ATM. Wait and see, I guess.
Oh, so realistically, AAMs on F16s are rail launched, not drop and burn style?
-
Oh, so realistically, AAMs on F16s are rail launched, not drop and burn style?
Absolutely.
-
I had opportunity to use the CRUS HOME function recently and noticed that the speed caret no longer jumps down in speed from MIL climb (faster) indication to level best range (slower) indication when you reach the indicated HOME altitude caret. Presumably I am using less fuel at 250KT than 310KT at the semi-level top of climb portion of the HOME profile but the speed indicated the faster speed until I got to the descent portion.
-
Texture issue that I already mentioned but I have discovered the problem. The German Tornado IDS has two texture sets; gray and green. However, the cockpit/wings model (2667) only has one texture set; grey.
I was hoping to add a second texture set to fix the issue but could not find a way to.
-
TGP/WPN page white/grey shadows in Harrier…. similar to masking of the TGP from fuselage/stores with F16, but this occurs in direct line of sight of target. Changing pitch slightly can remove it enough for targeting, but it’s a bit of a pain. Anyone else getting this?
-
TGP/WPN page white/grey shadows in Harrier…. similar to masking of the TGP from fuselage/stores with F16, but this occurs in direct line of sight of target. Changing pitch slightly can remove it enough for targeting, but it’s a bit of a pain. Anyone else getting this?
Confirmed, is a pain… Inventory stores and pylon numbers are also shifted left…
-
There seem to be missing tarmac textures at Kadena/Fukuoka. This occurs for me in both my ‘active’ install and my spare ‘clean’ install. In both installs this is apparent when I ramp start and when I 2D Recon from a built-in training TE. Both installs use Polak’s tileset.
Have not checked in Campaign and will do so, but I expect the same.
(Edit: )
From 2D recon in campaign …. same:
(Searched docs and threads and did not see this reported as a change or known issue for 4.33.)
-
One bug I noticed at night:
In the Block 40, the tail collision light is always “on” in fly by view. -
Jsow are still holy weapons, terrain and AI is not up those so player can get crazy amounts of kills with those. 40-60 units single single plane, single flight
Its fine that we get All high tech weapons but maybe those should not be in stock campaings in default. Red side gets wasted in first day.
Terrain offers zero cover to enemy and sam’s cant take out weapons and AI wont move units enough so its walk in park.
-EDIT- maybe bit too fast test. After some more test’s it looks like it is not so overpowered than it was. Not 100% sure yet, not enough free time to test more.
-
One bug I noticed at night:
In the Block 40, the tail collision light is always “on” in fly by view.Known issue. Should be fixed in an update later on
-
I’ve been hopping around to different squadrons during the campaign, trying different aircraft. Awesome.
F-15C, I assume is missing the ECM light texture, when jammer is turned onI know this setup is possible in real life, but I don’t think that every flight leaving the carrier should look like this. (14 amraams) It doesn’t feel very realistic. The AI needs to tone it down.
edit:actually, I don’t think the outer pylons can have 2
-
I’ve been hopping around to different squadrons during the campaign, trying different aircraft. Awesome.
F-15C, I assume is missing the ECM light texture, when jammer is turned onI know this setup is possible in real life, but I don’t think that every flight leaving the carrier should look like this. (14 amraams) It doesn’t feel very realistic. The AI needs to tone it down.
For day 1 in campaing that is fine loadout , if range is good why not. Its full war, red horde of migs incoming…not some terrorist gone hot secenario with rebel cesna as air threat
-
During our flight yesterday, in BAF MLU’s, we were en-route to a friendly carrier group and we had absolutely nothing on the RWR (Carapace). The exact moment I switched my FCR from GM to SEA, however, the three of us got several naval threat indications, at closer than 30NM. Don’t know if this is a bug until it is tested and confirmed more, but it did seem a bit too much of a coincidence to have happened by chance.
A few hypotheses:
- The CARAPACE is designed to always show naval threats, without requiring user input. Because BMS MLU’s still use Block 50/52 under the hood, maybe this automatic recognition does still need to be triggered somehow, e.g. by selecting FCR SEA mode for a moment? (probable)
- The moment my FCR starts scanning for sea contacts, ships know (is passive sensor simulation implemented?) and they start looking for me. (possible)
- The CARAPACE’s automatic naval threat designation is (incorrectly?) linked to the FCR SEA mode entirely, and will not activate in any other mode. (unlikely, I guess)
-
1 and 3 is clearly not the case, I can receive naval contact in nav mode / CRM.
To me is just a coincidence.