Preliminary 1.1.0.9 Change Log

[Grimes]

I wonder if "client" aircraft will work with the "inactive" feature. Also, can a tester kindly check if this new feature will effect a trigger involving an inactive group in a spawn. IE, Unit X in zone Y isn't true until Unit X spawns.

[STP Dragon]

I wonder if "client" aircraft will work with the "inactive" feature. Also, can a tester kindly check if this new feature will effect a trigger involving an inactive group in a spawn. IE, Unit X in zone Y isn't true until Unit X spawns.

 

Well, I'm not a tester but in my point of view this will not work.

In BS you was not able to deactivate a Client. If you don't want that a Client join a slot you have to constantly explode die aircraft after spawning by trigger.

 

And I think that a "not started" A.I. aircraft is in the zone.

 

Do you want to bet? :smartass:

[Grimes]

And I think that a "not started" A.I. aircraft is in the zone.

 

Do you want to bet? :smartass:

 

Sure, I'll wager a friendly bet, what'll it be?

 

But I'm basing my guess on the fact that land AI with "Visible before start" aren't "inside" a zone until they spawn.

 

Besides, I was curious about the client thing because A. It'll be super cool if it does work that way. B. I might need to adjust player counter triggers to accurately know how many aircraft are alive and active.

[STP Dragon]

But I'm basing my guess on the fact that land AI with "Visible before start" aren't "inside" a zone until they spawn.

Hm... that's right... Maybe I have to think about my bet. :D

We will see who has right.

 

 

Besides, I was curious about the client thing because A. It'll be super cool if it does work that way. B. I might need to adjust player counter triggers to accurately know how many aircraft are alive and active.

Yes I'm 100% with you. It would be awesome if it will work like this...

[latearrival]

That one was one of the main focus points for this patch. But hopefully nobody will need it because they'll now move to 64 bit

 

I'm very happy that v1.1.0.9 means I can have a nice sharp cockpit again. But I thought we'd established here that the problem wasn't a 32 bit vs 64 bit thing? http://forums.eagle.ru/showthread.php?t=74828&page=17&highlight=blurrie

 

I run 64 bit Windows, have a half decent system, run at 1280x1024, and I have to have textures set to medium to avoid/minimise stutters.

[Boulund]

I'm very happy that v1.1.0.9 means I can have a nice sharp cockpit again. But I thought we'd established here that the problem wasn't a 32 bit vs 64 bit thing? http://forums.eagle.ru/showthread.php?t=74828&page=17&highlight=blurrie

 

I run 64 bit Windows, have a half decent system, run at 1280x1024, and I have to have textures set to medium to avoid/minimise stutters.

 

I think he implies that most (not all) people that use 32bit do it because there has not been any free-track/facetracknoir alternative for the 64bit version. But since there now is, they will move to 64bit. :)

[joker62]

Please, when will be improved lighting at FARP?

 

This is persistent lack at sunset, dawn and night.

First screen, before to start mission, and second just started.

 

antonio.

[latearrival]

I think he implies that most (not all) people that use 32bit do it because there has not been any free-track/facetracknoir alternative for the 64bit version. But since there now is, they will move to 64bit. :)

My mistake. Thanks for pointing that out Boulund :)

[Nufsed]

For sure. Fix everything possible before moving on. It is just that it will be hard get perfection in such an advanced sim. Even FC2 and Ka-50 still have bugs. You fix somethings with a patch and then maybe break others. Stuff that may only be found after the patch is released to the public. There may be a point where I guess ED should move on. If 99% of things are working then I think we should all be happy.

 

Correct me if I'm wrong, but if the underlying code is bug free will it not benifit the next sim anyway?

[MadTommy]

The list looks great, but I hope the patch is the final patch and ED can focus on what is next. Thanks ED

 

I hope not....at least until everything (MP especially) is working as it should I hope ED keeps on patching!!!

 

QFT!!

 

Please patch this bad boy till it's perfect!.. a tall order no doubt, but there are still many issues in MP that if fixed would make me very happy.

 

Great list of fixes but the shortness on the MP list makes me :cry: (same ol same ol.)

Edited June 21, 2011 by MadTommy

[Nate--IRL--]

I'm probably way off here, but isn't DVADR the hud video camera? Does that mean this patch implements HUD recording?

 

It is cosmetic only.

 

Hmmm... I might be wrong... but wasn't the Black Shark integration patch supposed to come out with this update as well? :pilotfly:

 

No - this was meant to be a hotfix that morphed into full patch.

 

 

I think he implies that most (not all) people that use 32bit do it because there has not been any free-track/facetracknoir alternative for the 64bit version. But since there now is, they will move to 64bit. :)

 

Yep, that what I meant, sorry I should have been clearer. Either way it is fixed.

 

Nate

[REL]

- Master Caution Flashes/Warning Sound when Pressing Bleed Air leak test button.

 

Wait .. the Bleed Air Leak Test Button is functional? sins when?

Edited June 21, 2011 by REL

[Olgerd]

The list looks great, but I hope the patch is the final patch and ED can focus on what is next. Thanks ED

 

It is not the final patch.

[MTFDarkEagle]

sins when?

1.1.0.8 ;)

[Olgerd]

Are these all changes based on the real bird? I'm assuming so, but the HUD rework seemed like a big change that would have been in already?

 

Cheers, and amazing work ED!!

 

-HUD symbology was reworked in HARS mode – many symbols were removed from the display and some were returned. Fixed gun cross was implemented. Logic for some of elements (like TISL Cue Index) in HARS was updated.

 

There were bugs not addressed in previous patches

 

- APU and Left Engine do not require fuel pumps to be active.

 

Actually we will remove this from the list, as this was working in this way since release (or may be one of first patches).

 

- Laser code on TGP was made always visible.

 

It is "Nice-to-have" feature from one of later Suites.

[104th_Crunch]

It is not the final patch.

 

Thank you for the confirmation and ED's and the beta tester's hard work. Look forward to the future.

[SmokeyTheLung]

Thanks for the info

[Krippz]

Thanks for the insight Olgerd.

[Frostiken]

It is "Nice-to-have" feature from one of later Suites.

 

 

<_<

 

 

>_>

 

 

Does JHMCS qualify as 'nice to have'? :D

[Olgerd]

<_<

 

 

>_>

 

 

Does JHMCS qualify as 'nice to have'? :D

 

No it does not. :)

[Shake3000]

- Maverick will break lock now if missile FOV was changed.

 

Wow that's a major drawback. I bet it's realistic though.

[Olgerd]

- Maverick will break lock now if missile FOV was changed.

 

Wow that's a major drawback. I bet it's realistic though.

 

Yep. Same IRL.

[chaos]

Thanks for another huge list of improvements. May I be so bold and ask for one more? The TACAN distance counter doesn't show a 10th of a mile. It's been annoying me since beta1 (the things people get worked up about...). Anyway, I'm sure it's on the list. Here's to patch .10 ;)

[Frostiken]

No it does not. :)

 

You're right.

 

It's essential!

[LostOblivion]

"Removed" broken tree and FARP shadows?

 

Hey ED,

 

In your preliminary 1.1.0.9 patch notes you state that you are removing broken tree and FARP shadows. Are you removing tree shadows alltogether or fixing it?

 

- Lost