2024-03-29 12:24 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0003322NorthAndSouth[WHDLoad Installs Games] OCSpublic2019-01-30 22:08
Reportermahen 
Assigned ToJOTDProject InfoNorth & South (Infogrames)
http://www.whdload.de/games/NorthAndSouth.html
 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
Summary0003322: Cannot select unit on map screen after a few turns with CUSTOM1 or CUSTOM3 options
DescriptionHi !

This is an issue I talked about in another bugreport. I thought it would be more relevant to create a distinct one.

When using the CUSTOM1 or CUSTOM3 options (mapping infantry change to 2nd joystick button), after a few turns of play, it is impossible to select any unit on the map. Mouse does move, units do blink but the game is completely stuck as no unit can be selected/moved anymore.

In my case, it always eventually happens after just a couple of turns.
Steps To Reproduce- I select the CUSTOM1=1 or 3 options
- I select the French language
- I choose the 3 random events then start a game
- I move the 2 blue soldiers to catch the top left station and the harbour
- I start and win a battle
--> impossible to select an unit anymore on the map screen
Additional InformationHardware configuration : tested with both a MiST (AGA core 1.0, newcpu mode) and FS-UAE (A1200 mode). Basic WB 3.1 installation.

- whdload 18.1
- north&south slave 1.6
- os 3.1

Also I noticed that units on the battlefield cannot move diagonally. I don't remember if that is intended / is the normal behaviour.
TagsNo tags attached.
MachineA1200
CPU68020
CPUSpeed50
ChipSetAGA
GFXCardNone
ChipMem2 MB
FastMem32 MB
WorkbenchOS 3.1
KickROM40 - Kick 3.1
KickSoftNone
WHDLoad18.1
imported
Attached Files

-Relationships
+Relationships

-Notes

note ~0005005

mahen (reporter)

Issue still occurs with the new updated slave (1.7). Please tell me if I can help debug this issue :-) It makes it impossible to use the 2nd joystick button sadly.

note ~0006685

JOTD (developer)

I'm supposing that this is fixed since I rewrote most of the control part & replaced the joypad read routine by the newest version
+Notes

-Issue History
Date Modified Username Field Change
2015-11-25 16:25 mahen New Issue
2016-06-25 13:34 mahen Note Added: 0005005
2019-01-26 22:52 JOTD Assigned To => JOTD
2019-01-26 22:52 JOTD Status new => acknowledged
2019-01-30 22:08 JOTD Status acknowledged => closed
2019-01-30 22:08 JOTD Resolution open => fixed
2019-01-30 22:08 JOTD Note Added: 0006685
+Issue History