Any possibility trees in 4.32 ?

[timd]

Okay slightly weird question.
Is it possible to install trees into the 4.32 terrain ? I’ve gone back to 4.32 for a couple of reasons. The one thing I really miss is the trees !!! I suspect there is slightly more to it than just porting over the Terradata file. Anyway just thought I’d ask.

Thanks TIM

[Corsair]

I’m afraid not. I let people-who-know confirm or infirm, though…

[Dee-Jay]

Hi Tim!

Such an installer does actually exist (but unavailable for the moment), in fact, 4.32 + trees + few other features = 4.33 … It has been prepared on that pupose.

So (to answer your question without joking) no, it is not possible to have auto-gen trees under 4.32 …

Sorry

[timd]

I suspected as much.

For me 4.33 is incredible aside from two issues IMHO.
One, the change in key commands is a pain. Fine if you are flying every night and own a Thrust Master Warthog, not insurmountable, but a pain none the less.
Two, the show stopper for me, the dull low contrast HUD symbology which frequently makes even basic Alt speed direction impossible to read.

I suppose my ideal equation would be
4.33 + idiots alternative Key Commands (legacy 4.32) + brighter HUD = FLIGHT SIM PARADISE

TIM

[I-Hawk]

@timd:

I suspected as much.

For me 4.33 is incredible aside from two issues IMHO.
One, the change in key commands is a pain. Fine if you are flying every night and own a Thrust Master Warthog, not insurmountable, but a pain none the less.
Two, the show stopper for me, the dull low contrast HUD symbology which frequently makes even basic Alt speed direction impossible to read.

I suppose my ideal equation would be
4.33 + idiots alternative Key Commands (legacy 4.32) + brighter HUD = FLIGHT SIM PARADISE

TIM

Well it takes ~30 minutes max to fix/copy-paste/rewrite/whatever the key file as you want it to be, I know because I also have a “special” key files with special keys which as weird as it sounds includes some key commands which I’m carrying since I used to fly USAF ~15 years ago

About the bright HUD, honestly nither me nor anyone else reported something similar, I’m sure if there was a real problem someone would have already waved it as an issue. But for the minimum can you please post comparison of what you mean? thanx.

[timd]

Thanks for reply.
Key command problem surmounted although considerably longer than 30 mins…it’s an age thing and hey its falcon so it’s worth it.
HUD don’t understand . Same computer/screen/graphics card/settings 4.32 no problem 4.33 problem in bright conditions…go figure.
Seeing previous posts not alone but definitely not majority so I’ll have to go back to graphic settings see what I can do. If the worst comes to the worst I go back 4.32…going from the very best to just the best hardly a major loss.

TIM

[scar3tactics]

I’ve noticed that I have most of my HUD problems right on the horizon, especially above clouds. Interestingly, I found one way to fix it is to offset my view slightly. For instance if I look slightly up and position the HUD below the center of the screen, it becomes more readable. Using the ‘2’ view also improves it. I also noticed that when first switching to cockpit view(for instance if I was in external view then hit ‘3’ again) it’s readable for a second before washing out again. Maybe an HDR/glare issue?

[Tomcatter31]

@timd:

I suspected as much.

For me 4.33 is incredible aside from two issues IMHO.
One, the change in key commands is a pain. Fine if you are flying every night and own a Thrust Master Warthog, not insurmountable, but a pain none the less.
Two, the show stopper for me, the dull low contrast HUD symbology which frequently makes even basic Alt speed direction impossible to read.

I suppose my ideal equation would be
4.33 + idiots alternative Key Commands (legacy 4.32) + brighter HUD = FLIGHT SIM PARADISE

TIM

Hi Tim,

I’ve copied the 4.32 keystrokes file to my 4.33 folder and still use that one. I might miss some new functionality, but I haven’t found anything yet that I miss. I can fly like I always did.
I haven’t noticed a difference in the HUD contrast. To me 4.32 and 4.33 look the same in that regard. Sorry to see you have problems in that area.

[Dee-Jay]

*/!\ Do not use 4.32 keystokes on 4.33 otherwise, please, do not report for bug. /!*

You can customise 4.33 keystokes as you which and you can set it like it was in 4.32 manually no problem
Yes, it can be made in less that 30min as I did it in about 10 min (no need to remap EVERYTHING) just set what you are used to use)

HUD contrast: I do really see NO reasons to have any difference. Check your HDR setting in you .cfg (maybe it was desactivated in your 4.32?) or graphic card setting profile (maybe custom profile?) …
Try to reduce your screen contrast a very little bit.

[Tomcatter31]

Thanks for the warning. Could you elaborate a bit what can go wrong?

[Dee-Jay]

Callbacks compatibility/behavior (maybe also param syntax).

[timd]

Checked bms.cfg 4.32 install compared 4.33, hdr on in both.

Weird dual install on same computer same monitor same graphics card.

On closer analysis following repeat comparisons the problem in my set up appears to be the circular green shading in the centre of the HUD. In 4.32 it is more obvious. When the background is bright (clouds , bright hazy horizons) the HUD data in the periphery (outside the green central tint) washes out but within the green tint maintains enough contrast to be readable. In contrast (pun not intended) the 4.33 HUD has a much more subtle green central tint which unfortunately doesn’t prevent the washout in bright colours making it almost unreadable against bright clouds and bright hazy horizons.
Anyway that’s my mileage playing both back to back on the same system. I’ll revert to 4.32 but thanks for listening and most of all thanks for the massive amount of work the BMS team put in.

TIM

[Dee-Jay]

Enjoy Tim!

[Arty]

Well if u want some functions other than default it takes time. For me till 4.33 release didn’t had the time to pass to 4.33 keys