Update on 4.35 U2
-
That was it ! , we called it slip in a ditch, ….sliv oh vich …it was potent home made, and plumbs ring a bell
-
conversation is drifting…
Back to topic please.
-
-
-
-
-
Patience is one, virtue !!
-
U2 … why it takes that long…
Yeah, really sorry about that. Whenever we think we have a good candidate, we find another CTD. It’s a bit frustrating, at the same time rewarding to see all the progress we made so far.
I know Ive said this before but we are getting closer. Our candidate 27 is close to what I would like it to be. Not perfect, but good enough.
Still some tests ongoing, and sorry, no dates. But I wanted to say we are indeed getting there.
-
Come on, don’t be sorry, we’re not trying to date you. Do what you have to do in peace.
-
i anticipate for 4.36 then all will go slow i wish
-
@vfp:
i anticipate for 4.36 then all will go slow i wish
Your lack of faith is disturbing…
36 will kick ass!
-
_"Ambitious, considered all the people here’s skills…
But I like this behavior in a pilot." (more or less, Cmdr. Viper addressing to the scholars attending at the TopGun first day :D)_
With best regards to all.
-
One more report from the front…
This weekend we will go heavy on another candidate, our 30th.
There are no more known critical issues, which means all we knew that was wrong, we fixed: from very old bugs in Falcon core, to very complex bugs in our new rendering engine. Of course, new issues can show up as well, even the fixes might contain bugs.
There are still logic bugs, but the focus of this release is stability. This means we still have weird AI behaviour and some glitches. But we expect a lot less CTDs than before.
Fingers crossed here.
-
If this is truly supposed to be a simulation of real life, then remember that some weird AI behavior is realistic, because some people are weird.
-
One more report from the front…
This weekend we will go heavy on another candidate, our 30th.
There are no more known critical issues, which means all we knew that was wrong, we fixed: from very old bugs in Falcon core, to very complex bugs in our new rendering engine. Of course, new issues can show up as well, even the fixes might contain bugs.
There are still logic bugs, but the focus of this release is stability. This means we still have weird AI behaviour and some glitches. But we expect a lot less CTDs than before.
Fingers crossed here.
Don’t get this message wrong, 4.35 has not introduced weird behavior compare to previous versions
Ai « weird » behavior is mainly related to AG behavior that will not be fixed in 4.35
this behavior in AG is the same from 4.34, 4.33, 4.32 and all other falcon versions
To change this a full rewrite was needed but that’s not for 4.35
In AA I still to find a way to teach AI to not follow enemy in hostile territory for too long , but in the same time alloW them to engage in deep hostile territory when needed
This is not easy problem to solve , for now I don’t have the solution to get a reliable behavior. Problem beeing that AI are of course not « intelligent » they are just state machines
-
Is there some logic you could apply around closure rates vs duration of pursuit that might help a bit?
Sent from my iPhone using Tapatalk
-
Is there some logic you could apply around closure rates vs duration of pursuit that might help a bit?
Sent from my iPhone using Tapatalk
partially
-
Still very excited for U2 stability.
-
Tests are finished.
-