• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Heliosmaster

Recruit
41 Badges
May 20, 2015
1
0
  • Crusader Kings II: Charlemagne
  • Europa Universalis IV: Common Sense
  • Crusader Kings II
  • Ship Simulator Extremes
  • Sengoku
  • Europa Universalis IV: Res Publica
  • Magicka
  • Knights of Pen and Paper +1 Edition
  • Impire
  • Hearts of Iron III
  • Europa Universalis IV: Wealth of Nations
  • Europa Universalis IV: Art of War
  • Europa Universalis IV
  • Crusader Kings II: Sword of Islam
  • Crusader Kings II: Sunset Invasion
  • Crusader Kings II: Sons of Abraham
  • Crusader Kings II: The Republic
  • Crusader Kings II: Rajas of India
  • Crusader Kings II: The Old Gods
  • Crusader Kings II: Legacy of Rome
  • Europa Universalis IV: Conquest of Paradise
  • Hearts of Iron IV Sign-up
  • Crusader Kings II: Reapers Due
  • Prison Architect
  • Europa Universalis IV: Rights of Man
  • Cities: Skylines - Mass Transit
  • Europa Universalis IV: Mandate of Heaven
  • Europa Universalis IV: Cradle of Civilization
  • Europa Universalis IV: Rule Britannia
  • Europa Universalis IV: Dharma
  • Shadowrun: Hong Kong
  • Crusader Kings II: Conclave
  • Crusader Kings II: Horse Lords
  • Humble Paradox Bundle
  • Crusader Kings II: Way of Life
  • Magicka: Wizard Wars Founder Wizard
  • Europa Universalis IV: El Dorado
  • Cities: Skylines
  • War of the Roses
  • Victoria 2
  • Teleglitch: Die More Edition
How to reproduce this bug:

1) Open a Title
2) Click on claimants button
3) Leave the claimants panel open and click on another county/duchy/kingdom
4) Click again on claimants --> Nothing happens
5) Close the claimant window
 
Upvote 0

Servancour

Game Designer
Paradox Staff
4 Badges
Mar 15, 2012
1.569
7.915
  • Crusader Kings II
  • 500k Club
  • Paradox Order
  • Stellaris Sign-up
It's a known issue that the game may crash when using the claimant window, going back and forth etc. It has been fixed in our internal version already, though. So be on the lookout for the fix in a future patch.

Thanks for reporting.