You're either a pesimist or an idiot.
You can't be missing parameters. If some aer missing, then because the code relies on each paramter to interpret what should be happening, cars would glitch out everywhere, if that worked at all. Coming from someone who has written a few small things, I can tell you you can't just block off loose ends - the whole things works or it doesn't. The engine can't do only part of it because it all works with each other.
It's funny you call me an idiot, but then state problems that I specifically addressed as if I hadn't thought of them...
For instance, how can you use data files with less variables stored? Simple, you either dummy it in or make the code robust enough to handle missing variables.
Did you even see where I specifically addressed how to handle missing T and C variables or did you just want to spout off so badly you skipped over that?
See here:
https://www.gtplanet.net/forum/showthread.php?t=128481&page=360#post4052631
And that's just an ugly pseudo code example. If you honestly don't understand how a physics engine can function with older data models with less data, than you are just talking above your paygrade. I am certainly no professional coder, but the theory behind it and the practice is not something terribly advanced.
If you have ever imported and old model into a newer 3D modeling application, it's quite possible the newer one supports many features the old one didn't, yet it can still read in the old file.
And a very simple example Slipstream used earlier that might be better suited for you to understand is look at MP3 files. Currently they have all sorts of data stored about album title, art, artist etc etc. Back when they first came out the number of fields were much less, however modern music playing apps have no problems with these older files that are missing fields entirely.
Being backwards compatible happens all the time and it only shows how little you know aobut what you are talking about that you would say that's the huge hang up.
And secondly, they aren't going to have two seperate engines, one for standard cars and one for prem cars. You can't run them at once because of once again glitches when they occasionally meet and because it would be way way way way too hard for even a PS3 to run to complete engines at once. Hence standard cars can only be run with standard cars. This sounds even more limiting and unlike PD. Not only that, but then you have to have the code for teh engine for both. That takes even more space and would waste even more time.
And not once have I ever said there would be two seperate physics engines. I was very careful to say in fact that there would not be and even went to great lengths too illustrate and describe that point.
I believe that the engine has been remodeled and hence is acting differently, but that data is still teh same for all of it. Yes the weight of the car makes the car drive differently under the new physics engine, but they don't have to go and reweigh the car to find out its the same.
I have been saying exactly this... again, I know they are really long posts, but if you are going to bother to critique them, at least be decent enough to read them first.
THe main difference I believe between them is jsut the drivers cam, and the level of graphics. They need to be done seperately for each and every car. Hence you can have them both running together and each one has to be done up alone allowing PD to release the game with different standards.
Ironically I wouldn't be surprised if many of the cams are setup through some algorythm rather than manually per car. So far we have seen roof cams that look very different from mother roof cams and it seems quite possible they have just run some algorythm that says put roof cam centered left to right, directly over driver seat and 6 inches above the roofline or something.
Again, you said I assumed, which I might have, but you also said not to assume. You said that you didn't assume anything, and then a few post later, you said it was a general assumption
Yes it's called context. You were assuming what I meant and what I said and going with it as fact. When I say it's all general assumption, I am not assuming they actually did it, I am saying that in order to show you how something is possible, let's just generally assume these points for the sake of argument, I am not assuming any of it as fact, just using it as example of what's possible.
It's the difference between "I assume you meant to say THIS therefore I am going to go with it as if that's for sure what you meant" and "Well it's possible the 49ers will win the superbowl, let's assume that they recruit a star quarterback and he carries them the whole way, see it's possible then".
If you tried a little harder at the comprehension part and less at the defense part you might be getting somewhere....
saying assumption because he told me not to assume, but yet he was doing the same thing in a sense, but not admitting to assuming. To me, the word unlikely, alone, is an assumption, so he kind of brought it on himself. Just because he gives a LONG educated guess does not make it true, and therefore, it is an assumption/speculation.
You really need to learn the difference between assuming something to be fact, and making assumptions to illustrate a point. I am not assuming PD did it the way I laid out at all, I am only saying it's possible they did, specifically to show people who don't seem to comprehend how it could happen exactly how it could happen. When someone says "The 49ers could not win the superbowl because they have a crap QB) you don't have to assume the 49ers
will win the superbowl to say "well if they did recruit a star quarterback, then they
could win the bowl and thus it's not right to say they can't win the superbowl"