Yup, the Forza 2 .carbin formats are nearly identical to the lod 1-5 Forza 3 .carbin files, aside from small differences in the header and possibly in the vertex data as well. Should be pretty easy to implement after I start work on it. I've got a copy of Forza 1 around here somewhere as well, guess...

Yeah upload a few and I'll take a look at them sometime next week.

sommergemuese wrote:He "forget" to build in the UVs which were working perfect

My "forgetful" (aka lazy) self

Download Forza Studio (5.3.10)

Strings are usually null-terminated by a byte or word of 0's, depending on whether it's ascii or unicode you're working with. They can also sometimes prefixed with an integer value indicating their length, but null-terminated strings are usually more common.

My guess would be that you're changing the length of these strings, which isn't good practice in an executable :P To answer your question, yes there is a way to edit strings without corrupting the executable. Keep your edits just as long, or smaller, just make sure to add the character delimiter aft...

So I've taken a small break from my studies this weekend and did some major core changes to Forza Studio :) Currently I've integrated all of revelation's code into mine so it should be able to read any Forza 3 .carbin file now (let me know if you find out otherwise). Each piece also now has its own ...

shadowmoy wrote:here is a new version with some fixes :
http://www.mediafire.com/?mrnwzqinuem

Nice work

Any chance of open-sourcing this or possibly separating it into a dll so I can integrate it into my application?

Yeah, sorry about that. It's caused by a difference in string cultures where compared to North America, Europe seems to swap commas with periods for numerical values. Sommergemuese released a temporary fix earlier in the thread that you can use until I go back and fix it in my version...

the reason it looks good in games and some editors is because of the vertex normals in the file which hides the actual geometry's uneven surface. you can think of it as game fakery. That's fine with me :P. Honestly, I don't think it will be very feasible to try and recover any lost precision throug...

They look pretty damn similar to me :P considering the differences in the perspective and lighting, as well as the game obviously not being able to render physically real simulations at 30+ fps... Also, Forza 'Official' wireframe: Video here: http://www.youtube.com/watch?v=aTFMZTYGrWk http://img263....

Ernegien, let's not pretend what we are doing doesn't violate what the stiff suits want. extracting the models is ripping and playing with the models is not the same as pirating the game. let's not be hypocrites. I'm not being hypocritical, but merely stating that I would prefer this topic not be c...

Hi! I'm looking for this cars from Forza 3... 2010 Lamborghini Murcielago LP670-4 SV 2006 Subaru Impreza S204 2009 Ferrari California ...but i don't have the game... :( Can anyone send them to me please? Thankx a lot :] Please do not make such requests in this thread as I and many others are only g...

Thanks for taking the time and looking into this. It seems like you've fixed a few simple mistakes of mine (flipping xy offsets and some other stupid things :scaredy: ), cleaned up certain sections, and messed up others :lol:. I'm still pretty busy with other things at the moment but looks like the ...

Alright, I would have to agree with you there as I didn't entirely think things through. Regardless, I still feel the same as the models are capable of showing up fine in some instances. It is therefore an issue with the normals and or smoothing groups in my opinion.

I still don't believe that this is a precision issue. Each 16-bit float has a 10-bit mantissa with 1/2^10 precision. Since these values are bound between -1 and 1, this cuts the precision in half which equals 0.001953125. Now if it stopped there, yes I would agree this isn't enough precision but the...