For what it's worth, on my SD49225T-HN I'm also getting a 2/3rd or so green screen (and also the same right-hand portion as your screen shots) when using H.265
Then something weird... I decided to try it out on my phone using IP Cam Viewer, so I added the camera, made sure it worked, then switched to H.265.
It looked fine on my phone, then I looked back at
Blue Iris and it was working fine on there too.
So... what's different, you may ask? Nothing, honest!
Here's where it gets weird... so, I shut down the app on my phone and looked at anything else in the camera settings that I may have changed as well. I did also change to VBR, so I thought that might have done something? I switched back to CBR and 2048K... restarted the camera in Blue Iris... oh man, the green blob is back!
Changed CBR to 4096K thinking it needed more bandwidth... restarted cam; nope, still a green blob taking most of the image.
Now, remember, the app on my phone is shut down during this retesting... so I think "aha, it's failing in Blue Iris now, let's see what the phone app does". Start it up, and the image is fine. Well shoot. So while the app is running, I restart the cam in Blue Iris, and now it's fine again! What... ?
So then, Blue Iris and my phone app are both showing a good picture... I close my app, and BI is still good. Let's see what happens if I restart the camera in BI again. It's fine!
Okay... let's make some mostly harmless change on the camera like changing the max bit rate to another value...
The image in BI freezes when that change happens, so I have no choice but to "restart camera".
Green blob is back.
Open my phone app and bring up the camera, from BI I "restart camera" and voila, it's fine again.
My conclusion is that Blue Iris isn't initiating the RTSP stream properly, but when something else (another app) does so, then BI has no problem.
I won't pretend to know anything at all about the RTSP streams and how they work... apparently changing a setting on the camera will force any streams to restart, but is there some kind of initialization that an app has to do if it's the first guest to the party, so to speak? Something to tell the camera "if you're not already streaming, please start", and if it's not done right then you get over half of the image wiped out by some (presumably) default color or another... green in this case?
Well, hopefully my little troubleshooting and write-up helps him figure out the issue better and gives a solid, repeatable case study.