Skip to main content

More rockets and tech timeline.

I greatly reduced the rate of fire of the rockets and made them smaller. A single 60mm rocket now takes up the same space as a machine gun. A single vehicle should mount a large number of rockets to take advantage of their power.

I also added a delay after a weapon is successfully fired. This means the rockets will fire in a staggered volley instead of all at once. I tried both styles and this looks better and creates less logic spikes.

I think it needs more smoke and I'll be adding some rocket trails too.

I'm still unsure of where to put the rockets in the tech ladder. In real life the Russians developed their rockets before the German invasion. They were first deployed in 1941.

These early rockets were quite small though larger ones were developed later.
The Germans designed and tested their first rockets as early as 1940 but they were not deployed until 1941. Larger rockets were introduced later.

The rockets weren't mounted on vehicles until 1943, by which time the Americans had started producing their own rocket carrier.
I'm going to make the smaller rockets level 3, which puts them around 1941 levels of technology, while the larger ones will be level 4 which would put them around 1943.

Actually, now is a good time to talk about tech levels. I've set up the vehicle components so they follow a simple schedule based on tech levels from real life:
The current scope of the game is from 1936-1940, the first stage of the Vinland Crusade and the Northern Revolts. This makes equipment from level 0 to level 2 available, with level 3 and 4 equipment available as "prototypes" which can be bought at a much higher price and limited availability.

Each level allows the creation of a vehicle which is superior to those from the previous level. In theory if you had a vehicle which is all level 3, you could easily defeat a level 2 vehicle.

However, levels are split for each kind of technology and differ depending on faction.
For example, Vinland gets access to level 5 engine technology by 1943, but their weapons don't reach that pinnacle until spring 1948. The Europeans start out with level 2 technology almost across the board, but are much slower to adapt because of their long supply lines and entrenched military customs. Later in the war they are suffering a complete breakdown, with war weariness and revolts crippling their wartime economy. They lose their early lead and by 1945 they are only ahead on weapons and infantry.

This should give more interesting design philosophies, where some vehicles are far ahead in one area, but lagging in another.  


Comments

Popular posts from this blog

Automating Level imports from Blender to Godot

  Recently I've been making some levels in Blender an importing them into Godot. There are only about 7 or 8 shaders for each level, not counting dynamic objects which will be added later. But to improve rendering performance, it can be a good idea to split the meshes up into sections. At that point you might be faced with a list like this: Or it might be even more chaotic, if you didn't use simple names for the objects in your level. So it can take a long time to sort out all the meshes, make them unique and add textures and so on. Blender imports with simple Blender textures, or with placeholder materials. This is sometimes OK, but if your Godot shaders are very different to those used by Blender, it means applying new materials to every mesh object in the level when you import the scene. I found that during the design process, I was importing and readying a level several times before I was happy with the final layout. So at first I was wasting a lot of time. In Blender, I us

Upstairs / Downstairs.

I've decided to make my prefabs multilevel. Later this should allow me to add pit traps and other great stuff. It also makes it easier to line up stairs so that you can exit them on the same co-ordinates where you entered them. The prefab editor is pretty much finished, it just needs some code for loading up prefabs from a saved dictionary, so that they can be checked or edited. The entries will need to be forwards compatible, so I'll be loading each tile and then translating the indexes to a new array, that way if I add extra indexes or extra info (like traps or puzzles) I'll be able to update existing prefabs to work with the new standard. Click for a video.

Advice needed on tilesets...

I need some advice on which is the best way to handle building the dungeon. Right now I'm using prefabs for my dungeon, they have a north south east and west section for each "room": The basic tileset. This has several advantages, and also several disadvantages. Firstly I can have curved rooms, I can have tunnels and other interesting shapes. The tilesets can look quite nice with a little work. On the other hand I can't easily get the navigation data before building the map and once the map has been built I can't make changes to the layout, like having active pit traps or believable secret doors. Although the rooms are interesting, they are quite repetitive, and it takes a lot of effort to make even a few different variations. Also rooms are constrained to one size. A newer version of the tileset with a lot of variant parts for making more interesting rooms. To create a tile set is a real headache too. Planning how to lay out the UVs, trying to cra