Zap Andersson
Zap Andersson
I think it would be a mistake to pull this. As you yourself note, this is a solved problem in 3ds Max since a decade or two. The basic gist...
The crash in OSL is here, which is strange. The cause is that `module()->getFunction(name)` seems to return nullptr in this case, when name is “osl_fmod_dvdvf”? 
Here is a video showing me debugging the problem https://www.dropbox.com/s/xqnxaeqdkdckslo/osl-crash-with-fmod.mp4?dl=0
Personally don't care about the names as long as you pick them. Or I would have picked things like "osl:host" or similar :P /Z
I still care, and will start acting as if this was merged as of this second... :) **Edit:** Looking in my code, seems I cared since december 11:th 2018, LOL...
So turns out, I added this almost a year ago and then forgot, I blame the Chrismtas Schnapps: For anyone who cares, **3ds Max** OSL has for the last year...
@lgritz So based on last nights TSC discussion, it seems to be that we need an implementation for osl_fmod_dvdvf ? I think the reason I see that and you don't,...
Maybe it's CUDA version related, or maybe driver version related? I'm stuck on a slightly out-of-date driver coz my system runs Windows 8.1 ....
If it's just me, I'm fine with my local workaround. I just wonder, what the heck that line of code is supposed to do :P
Could we make it an option, so I don't have to live with a one line local change?