The Type 4 medium tank Chi-To (四式中戦車 チト, Yonshiki chūsensha Chi-To) ("Imperial Year 2604 Medium Tank Model 7") was one of several medium tanks developed by the Imperial Japanese Army towards the end of World War II.

Type 3 medium tank Chi-Nu (三式中戦車 チヌ, San-shiki chū-sensha Chi-nu, "Imperial Year 2603 Medium tank Model 10") was a medium tank of the Imperial Japanese Army in World War II. Like the Type 1 Chi-He, this tank was an improved version of the Type 97 Chi-Ha. It incorporated a Type 3 75 mm tank gun, one of the largest Japanese tank guns during the war.

The Type 97 Chi-Ha (九七式中戦車 チハ, Kyūnana-shiki chū-sensha Chi-ha or simply "Type 97/57") was a medium tank used by the Imperial Japanese Army during the Second Sino-Japanese War, the Battles of Khalkhin Gol against the Soviet Union, and the Second World War. It was the most widely produced Japanese medium tank of World War II. [7]

It was the most advanced Japanese tank to reach pre-operational level during WWII. Type 4 Chi-To in Kyushu, Japan, 1945, with what-if operational markings. Technical schematics drawing. All Tiger tanks liveries. Panther liveries and variants.

五式中型坦克（英文：Type 5 Chi-Ri Medium Tank），是作为“本土决战兵器”而研制的。 试制的样炮于1944年8月完成，8～10月间进行弹道性能试验，10～11月间在陆军战车学校先装到四式坦克上进行实用性试验，12月至1945年1月在中国东北北部 (日本人称为“北满”)进行 ...

Type 4 Chi-To-Tier 1,924 160 155 | 50 Tankopedia | 戰車世界閃擊戰 (WoTB)

2023年7月9日 · Type 5 Chi-Ri是基于Type 4 Chi-To底盘的加长版本（8个负重轮），配备了更厚更斜角的焊接装甲。 这包括前部护板上的75毫米装甲（2.95英寸），以及侧面、后部和炮塔上的25至50毫米装甲（0.98-1.97英寸）。

2013年3月23日 · \ ( \chi \) produces a letter that is slightly below the row, but I've seen in many papers a chi that is in the same line as the rest of the row)

To type Chinese, Enter fuzzy Pinyin (Pinyin without tones) into the Pinyin input box. For examples, hao and nihao. Use v for ü , e.g. lv When typing words with two or more characters, you can just type the first letter of each syllable. For example, ggqc for 公共汽车, daxs for 大学生, and gxing for 高兴 .

CHI协议最难的是什么，就是那一堆各种各样的事务，你不知道什么场景应该使用什么合适的事务，收到X事务又该回复什么事务。 相当于CHI给你制定了很多种（尽可能覆盖完全）场景及事务，你需要去了解，去认可，然后遵循，这就是协议。 所以，我们在这里对事务做个汇总，便于查看。 1.部分事务分为ptl/full ，这里不做区分。 2.事务名基本可以“望文生义”，也就是我们代码所推荐的“命名即注释”。 3.部分事务的行为并不完全确定，个人推测。 4.针对request …