Battlezone vector isue

JordanT

Member
Joined
Jan 11, 2017
Messages
324
Reaction score
9
Location
coquitlam, bc, Canada
Im having an isue with the vector cross hair wobbling back and forth when an enemy tank spawns in

it does not seem to matter if the tank is visible or just on the radar far away
that leads me to think it's something to do with a part of the game processing that bit of information
 
If objects are 'jumping' back and forth (like teleporting between position A and B) then that would point me to look for a digital cause, such as a bad counter. Same if the fault is only triggered at certain times, and is repeatable.
If objects are swaying back and forth, then that points to analog: either in the final output stages of the game PCB or the monitor or power supply.
You may have a combination of issues of both types. That's why it's nice to have an oscilloscope, or a second vector game, or spare components to swap in to try to narrow down the issue (or all of the above).
Self-test can also help. Flip the wee switch inside the coin door and turn on the game. Any beeps? Let's see a picture of what it shows on screen (and if any of those bits are moving).
 
I bet the score and the number of tanks left wobble too

Yes the tanks wobble the score is a bit off looking with the first digit sorta raming against the other digest (there zero)

monitor recapped ar2 boards recapped voltages checked on boards new bigblue

it's not the hole thing wobbling it's certin vectors at certin points in the game

the line that appears is predictable i think during the 3rd title screen when battle zone is scrolling up

every so often the score and tank indicator jumps close to the center of the screen for half a sec
also the mountains sometimes hover over the land
 
You most likely have something wrong late in the vector chain of the main board. This is where the counters and data shifters are that control the X and Y axes. (And in this case it's the x-axis that's the problem). Issues here will typically affect the graphics, but not throw errors in test mode, and not cause resets.

They are also some of the hardest to track down sometimes, if they are not any of the major chips, and/or if they are chips that are not completely dead, but are just operating incorrectly. It will likely be difficult for you to fix this on your own, without the proper tools and knowledge of the schematics.

The easiest thing to do would be to borrow another working main board, swap it out, and confirm that this is where the issue is. Then you need to start hunting. In your case however, it might be easier to find someone who is willing to repair it for you.
 
Back
Top Bottom