These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.
- GAME BUILD #: Current Build
- GAME PLATFORM: Steam
- OPERATING SYSTEM: Windows 10
DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.
Although aoe4 has been released, I still care about aoe3de.
The previous feedback topic description is not detailed enough, and can not be edited now. Therefore, in order to avoid ambiguity in the repair by the production team, I decided to make further detailed supplementary description on the model display bug of the Chinese meteor hammer cavalry.
Let me add that the current situation of meteor hammer cavalry is that the horse is upgraded normally (from 1 to 3, skip 2, everything is normal, and there is no need to modify), but the rider mistakenly stays at 1.
How often does the issue occur? CHOSE ONE; DELETE THE REST!
- 100% of the time / matches I play (ALWAYS)
List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!
This is a bug that continues from the original to the present.
What was SUPPOSED to happen if the bug you encountered were not present?
The correct form should be that the rider is the same as the horse, upgraded from 1 to 3, skip 2. that is, retain the two most different appearances.
Here I would like to remind the production team that the appearance of meteor hammer riders 2 and 3 is very close. Be careful not to make mistakes when correcting.
ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.
AGE3(Both the rider and the horse are the initial appearance, which is no problem.):
AGE4/5(Current error call result,The horse has been upgraded, but the rider’s appearance has not changed.):
AGE4/5(Results that should have been called correctly,Riders and horses are upgraded.):
By the way, this bug has lasted since the original version. Although the texture has been HD after De, it is still not used, which not only wastes the work of the modeler, but also makes the meteor hammer cavalry look very uncoordinated.
In a word, it is recommended that the production team repair this bug as soon as possible, although I also know that it is not worth mentioning compared with stability and balance.
Attach a SAVE GAME (.aoe3Ysav) or GAME RECORDING (.aoe3Yrec) of the match where you encountered the issue. Link it below if using an external file service.