.

Figure out how to parse the rear view mirror texture that's visible in the first person view. Currently that texture is not transparent at the edges.

@r1sc @JJJohan I downloaded this and got it to run on the proper Unity version, but I can't figure out how to get the vehicles to drive. I'm able to switch vehicles by changing the parameters in the 'game' object once the level is loaded, then I can click the camera and have it focus on the vehicle, but the vehicle doesn't drive. I can manually change the throttle and steering values on the car physics script once in-game, which makes the car drive, but actual input doesn't work.

It would be cool to revive this project. I'm a game developer, but not a coder. So I'm not sure how much I could actually contribute (if at all), but I'd love for this project to get revived. Even if you could help me get things working in the editor, that'd be cool. Thanks.

With most of the interior car interface out of the way now (with exception of the speedo/tacho) I figured I'd have a go at one of the real fun bits - the weapons.

We've got the models in place now and I've been able to squeeze even more data out of the GDF files through trial and error of editing the files in a hex editor and then observing the changes in the original retail version of the game (it's a lot easier to do that when the ZFS file isn't compressed)

We've got all the basics needed to at least make an attempt of firing the weapons.

Useful GDF bits:

• Ammo count
• Weapon health
• Weapon group
• Burst count
• Weapon mass
• Burst fire rate
• Weapon mesh
• Weapon facing direction (from VDF)
• Fire rate
• Firing sounds
• Projectile velocity
• Projectile damage
• Projectile mesh

What I've got implemented in a branch so far:

• Interface stuff
  • Cycling between weapons.
  • Weapon grouping.
  • Separator between front and rear facing weapons.
• Shooty stuff
  • Firing projectiles
  • Firing all grouped weapons.
  • Multi-shot weapons (e.g. fire-rite rockets fire rockets in a 3-shot burst before a longer reload pause)
  • Loading projectile models and textures

I've found that some weapons do not have meshes for the projectiles. Rockets generally do, but things like the 30-cal machine gun does not have a mesh - it only has a texture. Right now creating a 1x1x1 cube and texturing that, then shooting that out of the machine gun. It doesn't look great.

Some misc notes:

• I believe data blocks in the GDF files prefixed by 'O' refer to the projectile (Ordinance?) and 'G' refers to the actual weapon (Gun?)

• There is a mysterious string for each weapon in the GDFC block (which stores all the useful weapon info e.g. ammo, firing rate, etc.) - I can't find any references to this string elsewhere in any other files. Changing it doesn't seem to do anything in the original game. Examples are 'slg01' for gmlight.gdf and 'spp01' for gdumb.gdf.

• The GPOF block is not really understood. At first glance it appears to be the Forward, Right, Up and Position vectors for 4 separate objects. Zeroing this block results in projectiles hitting thin air as soon as they're fired.

• There's an ORDF block that seems to point at a number of XDF (sprite?) files and sound files, presumably used for hit effects.

• The OGEO block at the end of the GDF file refers to the name of the projectile with a matching .map and .geo file.

What I'd like to get done for a first pass & pull request:

• Figure out how the projectile is scaled - this should fix machine gun bullets from consisting of ghastly cubes.
• Try and solve the GPOF block data mystery and determine if it's actually needed.
• Simply reduce health of the entire vehicle the bullets hit (which will "explode" when their health reaches 0)

I'll be ignoring 'drop' weapons for the time being as they're a bit more complicated - e.g. oil slicks, fire, landmines

I'm not going to try and get XDF files for rocket smoke or projectile hit effects working yet. I just want the weapons to fire correct looking projectiles - after that I'll probably look at the missing bits.

I'll get some juicy screenshots in later - there's a few things implemented as noted above but I'd like to get it a little further along first.

Battlezone has had a very active community in the past might have more information about the file formats used in i76.

http://bzforum.matesfamily.org/viewtopic.php?t=172

https://bzscrap.org/downloads/Utilities/BZ1/

The Vehicle Configuration Files (.VCF) references component files for weapons (.GDF). For example WEPN........goilslck.gdf. These are parsed by the VcfParser, but they are not used anywhere at the moment.
Some GDF-files are not directly referenced by the VCF-files (e.g. Cup Holders).
Open76 should parse these GDF-files, including the geometry (if any) and attach them to the vehicle loaded.

1. Figure out how to parse GDF-files and write a corresponding GdfParser.
2. Discuss how the components should be attached to vehicles and finally implement this.

Hi,

I guess this repo is dormant now, but I have a question:
how would licensing work?
Can anybody just take the assets from Interstate 76 (3d models, but especially the soundtrack) and just use them? Do the users 'only' have to buy the game?

What if I make a new game with the assets?

Thanks,
Dirk

Hi,

I wonder which are the platforms you plan to support for Open76. It will be nice to have a Linux version of it.

The point of this issue isn't to get completely functional components, but to at least draw their UI elements on screen.

I've managed to decipher the ETBL blocks in the vehicles. These serve two purposes based on their flag. They are either reference images with one or more coordinates on the image to indicate where things go, or alternatively they are spritesheet images which are cut up into multiple sub-sections.

An example of a reference image - ZSY_.MAP (the lines and text were added for illustration purposes)

An example of a spritesheet - ZDUE.MAP:

The ETBL structure

The ETBL item structure

What I'd like to get working for this issue:

• [help wanted] Figure out how sprites are linked to items. For example, the '30cal MG' GDF weapon should be pointing at the 30cal_mg_on and 30cal_mg_off sprites, but I cannot find a reference to them anywhere, either by sprite index or by file name. In the Interstate 76 Gold Edition they ARE linked in the GDF by name (GDF is revision 8 instead of 7), unfortunately in the original game they are not - and I can't find them anywhere else!
• Draw the weapon brackets and ammo digit sprites.
• Draw the vehicle health sprites.
• Draw selected gear arrow (just always assume car is in 'D' for now).

Stretch goal:

• Draw compass
• Draw UI when car itself is hidden (i.e. hitting F1 key twice in original game toggles car interior on/off but always shows weapons, radar, etc.)

Right now, as a quick fix for terrain vs road height difference problems - the road hovers the terrain by some amount. This is ugly as the wheels sink through the road as they only collide with the terrain. The terrain also penetrates the road at some points.

A better "fix" would be to flatten out the terrain where the road is to avoid these problems.

Some objects in the map files are "stringed". This means they are laid out on the map as a continous sequence. Many fences utilize these features.

Currently, stringed objects does not align correctly with the map. Figure out how they should align.

"That Tony" has reverse engineered the map scripting runtime on his blog: http://hackingonspace.blogspot.se/2016/12/the-i76-fsm-processor-in-painful-detail.html

Open76 needs an implementation of these virtual machines to run single player missions.

The car physics needs a lot of work. Currently there are two different versions available. None of them feels like the "bowling-pin car model" in Interstate '76.

Make the car physics feel good. Preferrably like the original - or better :)