User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Defense AI occasionally not followed
Page:
 
Link
 
I give up also. No one makes mistakes. Blame it on the computer.

To Hazy,

Call me thick or whatever, but you didn't post the details of that output (ie shifts, underneath coverage, number of blitzers, blitzing %'s, LB depth...)

You may be right, and Bort may have wanted to look into it further....but with not enough info to test it out, he wouldn't be able to anyway.

Best of luck to you for the season.

It's just dots. No need to get upset.
 
thehazyone
NFL Replacement Refs SUCK
offline
Link
 
Still happening. Today it happened twice on the offensive side of the ball (I had the AI set to throw Medium Pass WR on 1st down no matter what and twice it ran the ball). Also happened one side on the defensive side. Only bumping this because I saw another thread mentioning the problem.
 
Larsonite
offline
Link
 
Shotgun 5WR
317C2MLPS

http://goallineblitz.com/game/replay.pl?game_id=206445&pbp_id=10838584

Please PM me if you really need more detail. Anyone who wants to comment on this particular play, please post it on this thread http://goallineblitz.com/game/forum_thread.pl?thread_id=1296417&page=1

Thanks and please no discussion of my example on this thread. This is for documentation of the issue. Discussion, as stated above, is on another thread.

-Larsonite
 
islander1
offline
Link
 
Originally posted by thehazyone
Still happening. Today it happened twice on the offensive side of the ball (I had the AI set to throw Medium Pass WR on 1st down no matter what and twice it ran the ball). Also happened one side on the defensive side. Only bumping this because I saw another thread mentioning the problem.


I love unofficial auto-adjust, don't you?

Offensively, the game is still calling short passing specific formations inside the 10 - resulting in halfback/fullback passes - even though the tested result is 100% medium pass play (to the WR or TE)

and yes, my QB is also set never to throw to the HB/FB. Although in both cases below these are clearly set pays designed to throw to those backs.

http://goallineblitz.com/game/replay.pl?game_id=206171&pbp_id=10793567
Matching Input
Input Named: 75 sec offense

Possible Outputs
20% TE medium (pass)
80% WR medium (pass)

and this one:
http://goallineblitz.com/game/replay.pl?game_id=206171&pbp_id=10795083

didnt bother posting the outputs, but I did look on this one as well.

This is the game not following our AI.
Last edited Oct 27, 2008 09:00:37
 
islander1
offline
Link
 
Originally posted by SteelersInsider
I give up also. No one makes mistakes. Blame it on the computer.

To Hazy,

Call me thick or whatever, but you didn't post the details of that output (ie shifts, underneath coverage, number of blitzers, blitzing %'s, LB depth...)

You may be right, and Bort may have wanted to look into it further....but with not enough info to test it out, he wouldn't be able to anyway.

Best of luck to you for the season.

It's just dots. No need to get upset.


No need to be a troll either. Some people actually try to win games, loldots be damned.

There's plenty of info for him to test this out. Not to mention the fact that, at least in the problems I've had with halfback passing, I've even spelled out exactly what's causing the bug.

The game is deciding what play set to call from before factoring in:

a) your own AI's designed distance for the pass
and
b) your QB's individual settings (i.e., the how often to throw to the backs IT).

This is a result breaking fail. If Bort's going to give us the ability to write our own playbooks, then how about allowing the sim to actually use it.

Now, I have no problem with a designed long pass route for the WR end up becoming a medium or even short if the situation need be...but at no point should the game be calling plays for the offense based on anything but from what the AI playbook tells it to.
 
Link
 
Originally posted by islander1
Originally posted by SteelersInsider

I give up also. No one makes mistakes. Blame it on the computer.

To Hazy,

Call me thick or whatever, but you didn't post the details of that output (ie shifts, underneath coverage, number of blitzers, blitzing %'s, LB depth...)

You may be right, and Bort may have wanted to look into it further....but with not enough info to test it out, he wouldn't be able to anyway.

Best of luck to you for the season.

It's just dots. No need to get upset.


No need to be a troll either. Some people actually try to win games, loldots be damned.

There's plenty of info for him to test this out. Not to mention the fact that, at least in the problems I've had with halfback passing, I've even spelled out exactly what's causing the bug.

The game is deciding what play set to call from before factoring in:

a) your own AI's designed distance for the pass
and
b) your QB's individual settings (i.e., the how often to throw to the backs IT).

This is a result breaking fail. If Bort's going to give us the ability to write our own playbooks, then how about allowing the sim to actually use it.

Now, I have no problem with a designed long pass route for the WR end up becoming a medium or even short if the situation need be...but at no point should the game be calling plays for the offense based on anything but from what the AI playbook tells it to.



When the game calls its own plays, that is a result of not having any instructions to follow. It doesn't work correctly 99% of the time and then randomly decide to go on its own. I encountered a play last game that wasn't what I called. Instead of complaining about it, I'm going to test out the play that is acting up further and find what the problem is and then keep that info for myself.

Bort would have to do the exact same thing. So narrow it down to the exact settings that aren't working and then post them here for Bort to fix or keep that info for yourself. What you *shouldn't* do is to post something with little to no information for Bort and have him spend hours and hours testing stuff out. He doesn't have time. YOU DO. If you have more than 1 play option, then narrow it down to 1. If it is still messing up, then change it to no blitzing or to no shift, or to no "basic settings" and force something in instead. Then when you have the EXACT settings that are broken, post it here and Bort can fix it in 15 minutes.

I'm just trying to keep the game moving along and not bogged down in silly little mistakes caused by a lack of a certain play that has already been fixed by the addition of the new plays for next season.

Do you want Bort to spend 3 hours tracking down a specific play that doesn't exist like 4-2-5 cover 3 zone, strong side shift, zone under, SS FS CB1 MLB blitz? Or do you want him to make a new screen play in that time instead? That's what it comes down to.
 
islander1
offline
Link
 
Originally posted by SteelersInsider
Originally posted by islander1

Originally posted by SteelersInsider


I give up also. No one makes mistakes. Blame it on the computer.

To Hazy,

Call me thick or whatever, but you didn't post the details of that output (ie shifts, underneath coverage, number of blitzers, blitzing %'s, LB depth...)

You may be right, and Bort may have wanted to look into it further....but with not enough info to test it out, he wouldn't be able to anyway.

Best of luck to you for the season.

It's just dots. No need to get upset.


No need to be a troll either. Some people actually try to win games, loldots be damned.

There's plenty of info for him to test this out. Not to mention the fact that, at least in the problems I've had with halfback passing, I've even spelled out exactly what's causing the bug.

The game is deciding what play set to call from before factoring in:

a) your own AI's designed distance for the pass
and
b) your QB's individual settings (i.e., the how often to throw to the backs IT).

This is a result breaking fail. If Bort's going to give us the ability to write our own playbooks, then how about allowing the sim to actually use it.

Now, I have no problem with a designed long pass route for the WR end up becoming a medium or even short if the situation need be...but at no point should the game be calling plays for the offense based on anything but from what the AI playbook tells it to.



When the game calls its own plays, that is a result of not having any instructions to follow. It doesn't work correctly 99% of the time and then randomly decide to go on its own. I encountered a play last game that wasn't what I called. Instead of complaining about it, I'm going to test out the play that is acting up further and find what the problem is and then keep that info for myself.

Bort would have to do the exact same thing. So narrow it down to the exact settings that aren't working and then post them here for Bort to fix or keep that info for yourself. What you *shouldn't* do is to post something with little to no information for Bort and have him spend hours and hours testing stuff out. He doesn't have time. YOU DO. If you have more than 1 play option, then narrow it down to 1. If it is still messing up, then change it to no blitzing or to no shift, or to no "basic settings" and force something in instead. Then when you have the EXACT settings that are broken, post it here and Bort can fix it in 15 minutes.

I'm just trying to keep the game moving along and not bogged down in silly little mistakes caused by a lack of a certain play that has already been fixed by the addition of the new plays for next season.

Do you want Bort to spend 3 hours tracking down a specific play that doesn't exist like 4-2-5 cover 3 zone, strong side shift, zone under, SS FS CB1 MLB blitz? Or do you want him to make a new screen play in that time instead? That's what it comes down to.


The problem is not in the AI. Offense is NOT complicated, and I provided the tested output myself.

The game calls short passing plays whenever it fucking feels like it inside the 10. not opinion. Fact.

What I want is the AI to follow my instructions. If I say 100% medium pass within a given scenario - I want it to call a damn medium passing play from the playbook.
Last edited Oct 27, 2008 21:41:10
 
Larsonite
offline
Link
 
I found out that against the WR Post Out my CB4 "occasionally" freaks out and doubles WR2 when the ball is hiked (literally leaving WR4 and doubling WR2) in a 317C2MLPC but not in a 317C2MLPS. Since I've changed the tactic it has yet to come back. It was weird because it was effecting different CBs but always CB4 and it only happened in a few games. Still, who sets more then one or two tactics against the 5WR Shotgun. It's ONE friggin play.

-Larsonite
Last edited Oct 28, 2008 00:19:15
 
RMiller517
offline
Link
 
Thread locked by moderator.
 
Page:
 


You are not logged in. Please log in if you want to post a reply.