• 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.
Code:
#Target must have at least one province of declarer's religion
		any_direct_de_jure_vassal_title = {
			owner = {
				OR = {
					character = FROM
					is_liege_or_above = FROM
				}
			}
			location = {
				ROOT = {
					religion = PREV
				}
			}
		}

Inside which set of brackets?
 
Code:
#Target must have at least one province of declarer's religion
        any_direct_de_jure_vassal_title = {
            owner = {
                OR = {
                    character = FROM
                    is_liege_or_above = FROM
                }
            }
            location = {
                ROOT = {
                    religion = PREV
                }
            }
        }

Inside which set of brackets?
Before the owner scope.
 
I1F1bVZ.png


Didn't fix it.
 
I'm having problems where the game crashes. It boots up just fine, all the way to the map screen, but as soon as I press Single Player to select a time period/ruler it crashes to desktop. I've confirmed this only happens when loading HIP, it does not occur with vanilla. Full HIP installment with VIET Immersion instead of SWMH, running on a Mac. Made a new installation sans NBRT+ because the installer says it might not be compatible with Mac but the same thing happens.
 
The only way I see that being possible is if a county within the duchy has a misplaced barony in another duchy. That way, the requirement about having a dejure title in a location with a different religion would be technically true.
Could you open up the ProjectBalance.txt CB file, and below line 1006 add "tier = count" and see if that fixes it?

Actually, that shouldn't fix it. Notice that it is any_direct_de_jure_vassal_title = { ... }. As it is a duke title by definition, it will only have count-tier direct de jure vassal titles.
 
I'm having problems where the game crashes. It boots up just fine, all the way to the map screen, but as soon as I press Single Player to select a time period/ruler it crashes to desktop. I've confirmed this only happens when loading HIP, it does not occur with vanilla. Full HIP installment with VIET Immersion instead of SWMH, running on a Mac. Made a new installation sans NBRT+ because the installer says it might not be compatible with Mac but the same thing happens.

Do you have all the portrait sets, including the new Turkish and Indian sets? And if not, did you apply the portrait fix when you installed HIP?
 
Actually, that shouldn't fix it. Notice that it is any_direct_de_jure_vassal_title = { ... }. As it is a duke title by definition, it will only have count-tier direct de jure vassal titles.
Hmm yeah, you're right. I don't see how the CB can be triggering then though.
 
Note the only reason that I don't have the ability to click send is because I'd just conquered the Isle of Wight off him (I entertain myself in situations where I can only take one province at a time by just claiming his capital).

Though it's annoying to have to spend so long warring against one duchy just to get all my de jure land.

GbGkKPm.png


Also, it doesn't appear to care for geographical restrictions.
 
Note the only reason that I don't have the ability to click send is because I'd just conquered the Isle of Wight off him (I entertain myself in situations where I can only take one province at a time by just claiming his capital).

Though it's annoying to have to spend so long warring against one duchy just to get all my de jure land.

GbGkKPm.png


Also, it doesn't appear to care for geographical restrictions.
I can't reproduce your issue at all. Could you perhaps send us the save?
 
Okay, whatever was causing that isn't in my current installation, so we shall never know why that happened.

Did you update? The code you referenced was part of a major 40-hours-awake run I did at isolating code everywhere for CTDs and sweeping over everything just doing fix-ups or finding bugs. I changed that very block you quoted fairly extensively, so perhaps I fixed your bug?
 
The installer encoding issue should be gone now.

Well, it won't dump an error on an encoding problem with your terminal locale (Windows-only issue, BTW). It _will_ still print some silly characters instead of the proper accents for the different installer translations if your system's configured locale doesn't match a console character set compatible with Windows-1252 or UTF-8. Mine runs the right character encoding by default, which is weird, and also why I didn't catch the errors in the first installer build we put up for this release.

For Windows, nothing short of writing a graphical installer is going to fully fix character set issues (or generally make the install process a lot more user-friendly). It's something I want to do, but I want to do a lot of things and only have so much time, apparently.