Hi @martin.klingler ,
So, the issue is that the rpict command is not getting the resolution values (-x and -y) assigned through grasshopper at present:
c:\radiance\bin\rpict -aa 0.25 -dj 0.0 -lr 4 -ad 512 -ps 8 -ar 16 -lw 0.05 -as 128 -ab 2 -pj 0.6 -dc 0.25 -dp 64 -ss 0.0 -pt 0.15 -dt 0.5 -dr 0 -ds 0.5 -st 0.85 -vf view\P1.vf Test_Mat01.oct > result\P1.hdr
A quick hack to fix this would be to add the values for x and y resolution manually in the batch file (in the case below I am trying to create a 1000x1000 pixel image. The final image would be clipped on the basis of -vv and -vh in the view file):
c:\radiance\bin\rpict -x 1000 -y 1000 -aa 0.25 -dj 0.0 -lr 4 -ad 512 -ps 8 -ar 16 -lw 0.05 -as 128 -ab 2 -pj 0.6 -dc 0.25 -dp 64 -ss 0.0 -pt 0.15 -dt 0.5 -dr 0 -ds 0.5 -st 0.85 -vf view\P1.vf Test_Mat01.oct > result\P1.hdr
The point-in-time simulations in HB[+] and HB are almost the same, as this still uses the decades old way that involves ambient caching. Actually, HB is slightly better implementation, because Mostapha has implemented an overture pass in that (Page 62 in this presentation from John Mardaljevic. You might already be aware of this, I am just adding the link so that others too know what I am referring to).
Till this lapse in the API for HB[+] gets fixed, I would recommend using HB for point-in-time simulations. You can find a simple Hydra example here.
Sarith