Jeremy Miller tweets (Senior Programmer at ISI)

Thanks Adrian.

I didn't think it would effect it, just curious.

I don't use multiview and I think most cars are OK in cockpit without. Its the open wheelers I don't like without it.

 

speaking of which, I think I read something here once about ISI using one big texture for the whole car instead of multiple sharper textures put together. Is this so and is it a big disadvantage?

 

Because you can, doesn't mean you should

 

I certaily would be pleased if rain is fixed and stability issues are minimized. I dont mind if 64bit support is included so far it is sufficiently debugged.

I've heard rumours of unstable being released by the end of this week. I don't know how reliable are them.
Did Jeremy tweet any clue about it?

enviado mediante tapatalk

 

Jeremy Miller @jeremymmiller · Jun 2

Builds over 724 will not show up on the 660 matching server. We are moving to new data layout and storage.



Jeremy Miller @jeremymmiller · Jun 4

My target (reserving right to change) is have unstable ready by end of next week. Updates to real road, possible 64 bit and new matcher



Jeremy Miller @jeremymmiller · Jun 5

To be clear. I said 64 bit was possible. Not a sure thing in the next build




Jeremy Miller @jeremymmiller · Jun 5

OpenSSL to 1.0.1h. Client and server side. Server side changes are running now. Build 660 is no longer vulnerable.

 

Thanks Ari, the rumors were quite reliable I see.

I perceive no signs of hurriness for including not ready things. I think this will be a good build. Realriad changes hopefully apply to rain and respective tyre cooling behaviour.

enviado mediante tapatalk

 

Nice timeline Ari, should set things straight, for myself anyway.

 

Heartbleed?
http://en.wikipedia.org/wiki/Heartbleed

 

Don't understand the necessity of encryption in an online racing game.

Maybe for Pay/License system?

 

The launcher sends your user/password and credit card to their webserver when buying/activating. It totally needs to go over SSL.

 

Yes of course, thought about online racng data at first.

 

I suggest reading Guimengo's posts one more time, it really is you who is misunderstanding. A LOT.

The post which Guimengo originally replied didn't mention unstable builds in any sense, it was about releasing 64-bit version to everyone before properly testing it.

 

I understood it as Guimengo's first message has been misunderstood already, but as you know I can not guarantee anything, I myself am married with translators.

 

They found seven more bugs, not as bad this time but one of the seven flaws they found was produced by the same coder responsible for the hearbleed bug. That is why 1.0.1h was released:

http://www.openssl.org/news/secadv_20140605.txt
https://github.com/openssl/openssl/commit/bd6941cfaa31ee8a3f8661cb98227a5cbcc0f9f3

 

@ TTupsi

I notice it's a new fashion to start screaming others misunderstood/misinterpreted, getting it wrong, misreading and so on, just to cover up they screwed up themselves and didn't get the point or were saying something they really shouldn't have.

I DO get it right. Why? As per post 1864, it is ALL about the unstable. (Well, for people just reading one or two posts and jump in trying to talk smart with al the others, it might not be as they didn't know what they were talking about.......)

And here's prove: the tweet from Miller was that the UNSTABLE might come out next week.......and HERE'S what your friend made of it:
This 64-bit doesn't have to be released the end of the other week. It can take longer time for testing and only be out in July,

Wel....... he points directly to the supposed release at the end of next week. We may take it he did read that part from this. We then also know he knows about the unstable because THAT was wat release was al about.

 

Who's your mistress, Chrome or Firefox?

My post had nothing to do with Jeremy's tweet, it was always to do with willz. ISI, myself, you, and a few others are in support of not releasing anything that should be in closed test environment to the public. Willz's post was in favor of it, bypassing the unstable RC completely. Lastly, I never changed my tone and I expect that once you realize everything that you'll feel the need to apologize for that outburst.

 

Navigator and Guimengo... shhh, you are actually arguing while agreeing with each other, its embarrassing... stop it.

I haven't got myself into testing the unstables (yet), but wasn't there a tweet that the 64bit .exe is not going to be working in multiplayer as of yet?
I can't seem to find that tweet to save my life, so sanity is in question here.

 

Not working yet correct. As for when its released who knows.

 

Currently Chrome but from time to time there is another


@Navigator
No there is no excuse for poor language skills you're right but it's the truth and it happens all the time.

 

Well I hope you don't die holding your breath.
You were referring to the "end of next week" and you go where ever the wind takes you just to get your truth.