Why is the programming in this game so flawed??

[Asane]

The AI is already really flawed, but what I am referring to is the if/else statements and the checking system in regards to collisions. This part of GT5 is so flawed. There's two ways in my opinion the game checks for this.

1) The way I see it in the license tests and the races is that there are two conditions the AI cars are in and those two conditions are either in a "neutral" state and a "braking" state. If you bump into the AI cars during their braking state then that results in immediate DQ otherwise a "bump" does not result in DQ.

2) This is where another part of the programming comes into play where the game checks for a certain amount of speed that you are in and if you are above a certain threshold which the game deems "appropriate" and you "bump" into an AI car, then that results in a DQ.

Both of these conditions only apply though when the player initiates the contact and not vice versa.

These systems should work in theory, but clearly they do not as evidenced by such license tests like IC-10 and IA-10. The main problem is that these two conditions that the game checks for are so stringent that they're downright unfair.

It seems to me that they should implement another "if/else" statement where if you are braking, then the 1st condition should be considered null where instead the 2nd condition takes its place.

In my opinion this can get rid of some of the "unfairness" that is present in some of these races.

Thoughts?

Anyway, this was just me ranting though. The other big problem is which part of your car should apply to these conditions, but that is another matter.

 

[Ya Pops]

Yeah, tis dumb. Also noticed that you'll often get away with tapping them if you're in the recommended gear for the corner.

 

[TommySalami]

It does suck, but if you're slamming into other cars during those races, you're not going to come in first anyway. The real problem is just the blind AI

 

[Asane]

It does suck, but if you're slamming into other cars during those races, you're not going to come in first anyway. The real problem is just the blind AI

That is not true at all. Even on some races bumping into the wall you can still one first.

 

[Goudvis]

If the programming were flawed you wouldn't be able to play the game.
You don't like what they've programmed.

 

[Asane]

If the programming were flawed you wouldn't be able to play the game.
You don't like what they've programmed.

Yes, you would be able to play.

Please learn your English, there is a difference between "flawed" and "broken."

And yes, for this part of code in the game I did not like the way they programmed it.

 

[MidianGTX]

The bottom line is that if you're good enough at the license tests you won't be smashing into anything. If you do, you clearly don't deserve the license, you're a danger to yourself and others.

 

[cygnus_zero]

but if you're slamming into other cars during those races, you're not going to come in first anyway.

Lol, what? Im pretty sure Ive won quite a few races by just playing bumper cars and mashing the AI off the road.

 

[Asane]

The bottom line is that if you're good enough at the license tests you won't be smashing into anything. If you do, you clearly don't deserve the license, you're a danger to yourself and others.

So... I'm a danger to myself and others when an AI car rear-ends me and I spin out...?

I'm not sure where you're getting at...

 

[Goes]

I think the main problem in scripted events is that they stick to the script to much. Just look at the slow paced top gear vw van challenge.. They always fake overtake attempts at the same points in order to slow you down. Then they push you off the race line when its there time to get back on it if you're behind the car they were meant to fake overtake.. or when you've slipped up and slower then they are supposed to be..

 

[Asane]

I think the main problem in scripted events is that they stick to the script to much. Just look at the slow paced top gear vw van challenge.. They always fake overtake attempts at the same points in order to slow you down. Then they push you off the race line when its there time to get back on it if you're behind the car they were meant to fake overtake.. or when you've slipped up and slower then they are supposed to be..

The scrips are another problem, but I was referring to specifically was only collisions.

 

[speedthrill]

I think the main problem in scripted events is that they stick to the script to much. Just look at the slow paced top gear vw van challenge.. They always fake overtake attempts at the same points in order to slow you down. Then they push you off the race line when its there time to get back on it if you're behind the car they were meant to fake overtake.. or when you've slipped up and slower then they are supposed to be..

This is only in the special events to be honest and it's there for a reason, All GT's in the past had it like this too. But the AI reacts and changes it's line when you get close (with a wheel this is). With a controller things get different however... Huge quick inputs, unnatural, offcourse make you believe shortly that it's ai's fault. But once you're in a wheel setup, everything changes...

 

[JTSnooks]

What annoys me is when I get disqualified for holding the racing line and the AI runs into my rear quarter-panel.

 

[Asane]

What annoys me is when I get disqualified for holding the racing line and the AI runs into my rear quarter-panel.

lol That's the exact problem that I was trying to address in my 1st post.

 

[Stonemonkey]

I think the main problem in scripted events is that they stick to the script to much. Just look at the slow paced top gear vw van challenge.. They always fake overtake attempts at the same points in order to slow you down. Then they push you off the race line when its there time to get back on it if you're behind the car they were meant to fake overtake.. or when you've slipped up and slower then they are supposed to be..

I doubt they're scripted.

 

[Pesmerga7551]

It does suck, but if you're slamming into other cars during those races, you're not going to come in first anyway. The real problem is just the blind AI

Some of the tests the best method is by slamming into cars. When I destroy tests in S license, that seems to be the secret. Lines in the inside are hogged by the AI cars 90% of the time, so you have to slam into the pretty much and hope to not be DQ'd. Well, maybe not slam, more like grind.. Anyways, you need to take the insides to get insanely fast times. And lets face it, the hard part of these races is avoiding the computer, as they do try to place them in front of you. You need to learn to take what they give, either be side-bumping or not. Like on the L.Seca trial, I get in 1st with I believe 4 turns remaining. The license trials are pretty easy for good drivers, the hardest is catching that damn GT-R. I think it's S9, but not sure. Need to know great lines on this one. If you ask me, bump passing on the inside is key.

 

[Goudvis]

Yes, you would be able to play.

Please learn your English, there is a difference between "flawed" and "broken."

And yes, for this part of code in the game I did not like the way they programmed it.

No, you don't like what they've programmed. The way they've programmed it, is very good.

 

[ECGadget]

My conclusion: The scripting should work in theory, but it is flawed because it doesn't seem dynamic enough. Only some events are set, so triggers are not complete. I'd say the script could do with more event possibilities. But still, its not too bad...

 

[Goes]

This is only in the special events to be honest and it's there for a reason, All GT's in the past had it like this too. But the AI reacts and changes it's line when you get close (with a wheel this is). With a controller things get different however... Huge quick inputs, unnatural, offcourse make you believe shortly that it's ai's fault. But once you're in a wheel setup, everything changes...

Yeah, haven't noticed that kind of behavior outside of special events. However in car views do tend to help a bit in judging how hard you're steering into a corner.. gave up on my wheel setup until my gamestand pro thing arrives. Ironing board + force feedback wheel tends to jump around

 

[Predwolf]

One might argue that if you're getting hit from behind, you're a slow driver, and still a risk to everybody on the track, hence the DQ.

 

[Asane]

One might argue that if you're getting hit from behind, you're a slow driver, and still a risk to everybody on the track, hence the DQ.

This could be true, but one might be able to argue as well that the AI should be smart and skilled enough to not rear-end me.

And I guess then that the "normal drivers" who are the ones that drive slow in the Nurburgring are a danger to everyone on the track and not the other way around...?

 

[Ya Pops]

No, you don't like what they've programmed. The way they've programmed it, is very good.

Opinion .




Edit: there ya go.

 

[Asane]

Opinion.

Opinion is good my friend, if stated with support otherwise people will not care.

 

[Ya Pops]

Opinion is good my friend, if stated with support otherwise people will not care.

Sorry, forgot to put the rolleyes smiley.

 

[bodger]

The AI is already really flawed, but what I am referring to is the if/else statements and the checking system in regards to collisions. This part of GT5 is so flawed. There's two ways in my opinion the game checks for this.

1) The way I see it in the license tests and the races is that there are two conditions the AI cars are in and those two conditions are either in a "neutral" state and a "braking" state. If you bump into the AI cars during their braking state then that results in immediate DQ otherwise a "bump" does not result in DQ.

2) This is where another part of the programming comes into play where the game checks for a certain amount of speed that you are in and if you are above a certain threshold which the game deems "appropriate" and you "bump" into an AI car, then that results in a DQ.

Both of these conditions only apply though when the player initiates the contact and not vice versa.

These systems should work in theory, but clearly they do not as evidenced by such license tests like IC-10 and IA-10. The main problem is that these two conditions that the game checks for are so stringent that they're downright unfair.

It seems to me that they should implement another "if/else" statement where if you are braking, then the 1st condition should be considered null where instead the 2nd condition takes its place.

In my opinion this can get rid of some of the "unfairness" that is present in some of these races.

Thoughts?

Anyway, this was just me ranting though. The other big problem is which part of your car should apply to these conditions, but that is another matter.

LOL - it sounds like you have read a beginners guide to VB and you are now doing a 'educated' critique on how you think they have slipped up on the AI and collision detection.

I don't think it is simple as you think it is.

 

[MidianGTX]

Edit: delete.

 

[Devedander]

LOL - it sounds like you have read a beginners guide to VB and you are now doing a 'educated' critique on how you think they have slipped up on the AI and collision detection.

I don't think it is simple as you think it is.

What he is doing is covering the logic process. The logic process is really that simple: Decide what will happen and what the defining factors are for when that happens.

This is the same for whatever language you want to program in from COBAL to C++ to Perl.

While the actual functions that handle the decision of what to consider a DQ and not is certainly complicated, the ruleset that guides those fucntions is probably about that simple.

 

[RedSuinit]

I am getting so tired of people complaining about the AI in the license tests. It's called a test for a REASON. There are RULES to these tests that don't apply to normal races, like getting DQ'd for hitting an AI car. They're a part of the rules for the test. The normal races is the ONLY place where you should be judging AI, collision physics, anything of that sort. Why? Because the tests are scripted in every way, and are done so because they are TESTS.

One other thing. While we may not "like it" that pretty much every time you touch an AI you get a DQ, that's how it is. It's a rule, and one that we all know exists in the license tests and TGTT. To complain about it is like complaining about the time limit on the SAT ACT or MCAT.

 

[jinjin12]

The AI is already really flawed, but what I am referring to is the if/else statements and the checking system in regards to collisions. This part of GT5 is so flawed. There's two ways in my opinion the game checks for this.

1) The way I see it in the license tests and the races is that there are two conditions the AI cars are in and those two conditions are either in a "neutral" state and a "braking" state. If you bump into the AI cars during their braking state then that results in immediate DQ otherwise a "bump" does not result in DQ.

2) This is where another part of the programming comes into play where the game checks for a certain amount of speed that you are in and if you are above a certain threshold which the game deems "appropriate" and you "bump" into an AI car, then that results in a DQ.

Both of these conditions only apply though when the player initiates the contact and not vice versa.

These systems should work in theory, but clearly they do not as evidenced by such license tests like IC-10 and IA-10. The main problem is that these two conditions that the game checks for are so stringent that they're downright unfair.

It seems to me that they should implement another "if/else" statement where if you are braking, then the 1st condition should be considered null where instead the 2nd condition takes its place.

In my opinion this can get rid of some of the "unfairness" that is present in some of these races.

Thoughts?

Anyway, this was just me ranting though. The other big problem is which part of your car should apply to these conditions, but that is another matter.

no offense but this shows how noob you are at programming, just cause you know some noobie stuff you think you suddenly know enough programming to judge them? it isn't as simple as if/else statments. also, with the ps3, they are also using the ps3 assembly language, and manually manipulating registers and etc....ain't simple like you think. learn more about programming, hardware architecture and design, and embedded systems then come back and try to make a valid argument. now i understand you're only trying to cover the overall simple aspect of it, but it also seems like you just read a "learn to program in 24 hrs" book and now think you are all that

moreover, you can't say the programming is "flawed" if you haven't seen their code, which is probably made up of several different languages, not just c++

 

[bodger]

What he is doing is covering the logic process. The logic process is really that simple: Decide what will happen and what the defining factors are for when that happens.

This is the same for whatever language you want to program in from COBAL to C++ to Perl.

While the actual functions that handle the decision of what to consider a DQ and not is certainly complicated, the ruleset that guides those fucntions is probably about that simple.

I'm sure he is.

But this isn't open source. I don't think DP are looking to this poster for advice.