Completed research in multiplayer does not show on the intelligence display screen. #3085
Comments
Per commented There is an intelligence display screen in multiplayer? |
Mysteryem uploaded file |
Mysteryem commented Attached an image of the intelligence display in master_20111204. There used to be a video played in the top right box which was differnt depending on what kind of research it was. I don't have sequences.wz to test to see if it still shows. The data for each of the research topics is taken from the resmessages files in mp\messages and base\messages, the 'MsgName' column in research.txt gives what researchmessage each research topic should use. |
cybersphinx changed priority from |
cybersphinx changed milestone from |
cybersphinx commented Broken in 82f4369beffd89431b743492abb04a0684c67aec. |
cybersphinx commented ... reverting needs a converter from .rmsg to .ini. |
zany commented Replying to Warzone2100/old-trac-import#3085 (comment:3):
|
scorgi commented Not only multiplayer, in skirmish mode was an empty window, too (#3275) |
cybersphinx changed status from |
cybersphinx changed resolution from `` to |
cybersphinx commented Readd skirmish/mp research messages, converted to .ini. Removed in 82f4369beffd89431b743492abb04a0684c67aec. Fixes #3085.
|
cybersphinx commented Readd skirmish/mp research messages, converted to .ini. Removed in 82f4369beffd89431b743492abb04a0684c67aec. Fixes #3085.
|
2 similar comments
cybersphinx commented Readd skirmish/mp research messages, converted to .ini. Removed in 82f4369beffd89431b743492abb04a0684c67aec. Fixes #3085.
|
cybersphinx commented Readd skirmish/mp research messages, converted to .ini. Removed in 82f4369beffd89431b743492abb04a0684c67aec. Fixes #3085.
|
keyword_research_f5_intelligence_display
resolution_fixed
type_bug
| by MysteryemCompleted research in multiplayer does not show on the intelligence display screen. Works fine for the campaign though.
Works as expected in master_20111204, but not in master_20120109 and later
Issue migrated from trac:3085 at 2022-04-16 08:48:48 -0700
The text was updated successfully, but these errors were encountered: