Discussion of Changes and Features 4.32 to 4.33
-
Bugged radar contact speed is in full 10 knots.
RWR is no longer dead on precise.
-
Could the old TE from 4.32 still be working in 4.33?
-
No.
Read the BMS Manual p17.
Use Mission Commander to convert your 4.32 TEs.
-
mission commander can convert te’s.
-
The TFR/FLIR implementation is phenomenal. I have grown to hate TF fly ups already (in a good way). I think I need to bind keyboard “A” to the TF advanced button.
I did read that IVC doesn’t require port forwarding anymore but today I failed to host until I re-added port forwarding (UDP 9897-9899).
I’m constantly surprised by the block-specific avionics changes. The INS was flashing ready at only 4 minutes in this newer model. The self-test MFD patterns for different ages (color cube vs. green monochrome).
The GPS LIST page I think is new.
I noticed the CRUS TOT mode wasn’t highlighted by default, at least on one model.
Different AIM-9 models have different DLZ and much more accurate predictions than before. The smoothness that the seeker “settles” on the target is pleasing. I dare to test later if it targets the hot engine end or just model center. I wish TD was able to be caged on good tone (if that’s real behavior).
I think with improved waypoint timing behavior for AI the takeoff times are much loser (more free). I get takeoff clearance 2+ minutes early. Although it was funny ATC said “position and hold” and then yelled at me for lining up and wait. I notice my AI wingman did a single ship departure (no form line up, 3-4nm trail) when we were heavy AG loadout in semi-bad weather.
The 10-point approach pattern is wonderful. After a quick read I feel more understanding with ATC’s plan and it flows more smoothly.
I notice master caution can’t be cleared before start. I used to use it as a crutch when my idle detent worked.
I can’t wait to play with Maverick and TGP with ABC handoff.
I notice the E/N prefix ICP code (2,4,6,8) requirement but south latitudes and west longitude aren’t enterable (at least in Korea?).
I saw that the RWR was giving directional indications for some bad but unidirectional indications for longer wavelength. Cool. RWR seems much less magical.
The autopilot and WP auto sequencing is much smoother than before without the left-right-left waggle flying through the point.
The B/D model fuel gauge has the proper balancing red paint markings for the balance unique to the 2-seaters.
-
Im loving the EEGS funnel now… having the lines in the targets POM helps a lot!
-
I noticed the CRUS TOT mode wasn’t highlighted by default, at least on one model.
That’s how it is in the real jet. See Dash-1 p65.
I notice master caution can’t be cleared before start. I used to use it as a crutch when my idle detent worked.
That’s how it is in the real jet. See Dash-1 p168, 174, 179 etc etc.
I can’t wait to play with Maverick and TGP with ABC handoff.
Challenging but rewarding
I notice the E/N prefix ICP code (2,4,6,8) requirement but south latitudes and west longitude aren’t enterable (at least in Korea?).
Why would you want to for Korea? In any case it’s a code limitation currently.
I saw that the RWR was giving directional indications for some bad but unidirectional indications for longer wavelength. Cool. RWR seems much less magical.
Much more realistic, which means you really need to keep up your visual lookout and task prioritisation if you don’t want to be surprised by a MiG popping up on your six, which they will do as they are much much better at intercepts now
-
Any one noticed anything in campaings? Looks like god eye Intel is gone ??
-
campaign saves .ini files.
-
Using cntl + z then r to bring up the frame rate will also periodically show the RAM usage, video memory usage, and page file size real-time.
-
Using cntl + z then r to bring up the frame rate will also periodically show the RAM usage, video memory usage, and page file size real-time.
use now alt + c then f to show up the frame rate (by using the new 4.33 key files)
BB
-
Load the aft with TGP, then go lock a ground target and watch the TGP head moving from external view…
-
AI is no longer prey. It can put up a real fight… :shock:
-
I did read that IVC doesn’t require port forwarding anymore but today I failed to host until I re-added port forwarding (UDP 9897-9899).
Wherever you read that it is incorrect. Hosting still requires port forwarding.
-
If you guys are talking about hosting IVC and not the game itself then the information provided to the manual team was wrong
and there is a mistake in the manual indeed -
You’re right, I wasn’t clear or specific enough: an IVC server will not work behind a NAT unless appropriate port forwarding is enabled. This hasn’t changed for the IVC server since day one. The only new news in this area is that the server can now use ports other than the defaults but of course if you change from default ports then the port forwarding rules have to be updated to match as well.
-
BMS Keystrokes - Defaults is possible in BMS 4.33 ??
-
I’m loving what i see with 4.33 from the trailer and what i’m reading here, just have a few questions,
- Will i be able to carry on my saved campaign from 4.32? (guessing i cant but no worries- will start a new one)
- Will i need to configure the commands for my X-55 from scratch?
Had problems lately with my PC but will be getting back on Falcon tomorrow and what great timing. Feel like the release of 4.33 is compensating me for my recent problems, just hope i dont get anymore!
-
I’m loving what i see with 4.33 from the trailer and what i’m reading here, just have a few questions,
- Will i be able to carry on my saved campaign from 4.32? (guessing i cant but no worries- will start a new one)
- Will i need to configure the commands for my X-55 from scratch?
Had problems lately with my PC but will be getting back on Falcon tomorrow and what great timing. Feel like the release of 4.33 is compensating me for my recent problems, just hope i dont get anymore!
4.32 saved campaigns will not work.
As to your X-55, bring over your keyfile from 4.32 -
BMS Keystrokes - Defaults is possible in BMS 4.33 ??
4.32’s .key are to be avoided in 4.33
If you use it, do it at your “own risks” and please … no bug-report in case of use of non 4.33 key map file.