Maybe. 2.5 and 2.6T can do H.265, but only on the highest resolution. If it can hadle this the lower settings I require shall be noch problem for the cam.
So, how to set it up?
I think maybe it is the 60Hz that is the issue more than the resolution, H265 takes too long.
This might be right for 1080P. The higher the resolution the bigger the advatange of H.265. Especial with 4k you can see the difference.
That is just not the case for dashcam footage. If it is a a video of a TV studio with simple images and little movement then certainly H265 does better, most movie footage is also better, largely because movies use massive processing power and a lot of time to produce "perfect" compression using variable bitrates, but for dashcam footage using constant bitrate compressed in real time, H265 does not do better than H264, even at 4K.
H.265 does have to be licensed, but I think the cost is small.
Depends on how many devices you are producing. For someone like Sony, or Samsung then yes, it is insignificant, but for the manufacturers who only make dashcams, it is very significant and with risk of being sued even after you have paid, since license requirements for all parts of H265 are not clear!
I'm transitioning to preferring H.265 for archiving video for general (non dashcam things) but i'd think considering the potential low priority implementation and high demands on hardware 265 has i would stick with H.264.
For dashcam video, I recommend using VP9 instead, or if you have sufficient processing power use AV1, they do a better job than H265.
If someone has been running 265 for and extended period and found it reliable and useful it would be nice to hear.
H265 on the Viofo cameras works fine, it just doesn't provide any advantage over H264!
For some people it does work better on their computers, basically people using Apple products, so that is a good reason to use it on the dashcam, otherwise it is of no advantage.