I might have a little bit of explanation about this matter.
The way this game choose the H scene is by using a random number generator that has minimum number and maximum number set like this.
View attachment 1068085
from this figure; this is a script using for choosing a H scene in the last boss fight (empress xeno , queen xeno , whatever xeno just call her bitch), H scene number 42 and H scene number 43.
The way the game choose the H scene is by using the random number generator (int num) with the range set from 0 to 10, after that Grimhelm set a condition further that
if the random number is less than or equal 5; int num will equal to 0 -> int num = 0 -> this.GM.Hscene_Num = 42 + 0 -> this.GM.Hscene_Num = 42 -> get H scene number 42
if the random number is more than 5; int num will equal to 1 -> int num = 1 -> this.GM.Hscene_Num = 42 + 1 -> this.GM.Hscene_Num = 43 -> get H scene number 43
*** note that not all monster that has 2 H scene use the exact code , they use similar but more simple code (use RNG then less than or equal 5 get scene X, more than 5 get scene Y) ***
the problem is the random number generator that Grimhelm use is a little bit unbalanced.
From
You must be registered to see the links
Return a random integer number between min [inclusive] and max [exclusive] (Read Only).
Note max is exclusive. Random.Range(0, 10) can return a value between 0 and 9.
If you read this explanation and go back and look at the code you will notice that the chance of getting scene 43 (6 7 8 9 ) is less than scene 42 (0 1 2 3 4 5); increasing the RNG range to 12 might fix this unbalance , but noted that tinkering something that work just fine might break something and make it not working properly anymore.
*** Edit ***
From my case , KMod, that also use the RNG to choose the dialogue to be displayed , the max number set in the RNG code can still get chosen but rarely get chosen -> only way make it get chosen the most is narrow down the range of RNG (in my case, once I use range 1 to 4, number 4 got chosen from time to time but less frequent than number 1 , 2 , 3)
From the scene that you complain that you never get, it is either the RNG code is super unbalanced that you cannot get that scene or Grimhelm forget to add a way to get this scene (forget to add Hscene_Num of this scene to monster) from all of this further investigation is needed and to the way to fix this in dnSpy is
1. Find which scene is this from tag Hscene_num
2. Use that number to narrow down which monster is this
3. Check the code about choosing H scene; if something is wrong there , just fix it
this is the hard way
the easy is to say "fek it" and press F1 in gallery screen