about ISF package with m4l
Hey guys,
I am building a m4l jitter device and I'm not sure about certain things regarding the ISF package.
I noticed that the package needs to be separately installed and compiled for windows and mac. Am I right?
Also, on some computers it runs the shader I'm using with it, but on other computers it's just empty, the code is missing, although I'm not exactly sure why it's happening because I didn't receive proper feedback yet from the testers. Some of them might already have the ISF editor on their computer and have the path for the ISF object.
My question is: does it mean I need to include the shader file with my amxd as a separate file and provide the path or can I actually compile it into the amxd file somehow so the code just stays there?
the isf object can load files outside of the standard isf library location, so you should make a copy of the file, rename it, add it to your amxd project folder and consolidate it with your project, and load that version in your patch
Thanks Rob!
I tried it, but it doesn't work. The files are renamed, copied to the folder and consolidated with the project, I provided the attribute @file blablafilename, but when I reopen the patch the isf object doesn't contain anything. I tried to send the read message with the exact filepath, but that also doesn't work. The only message that works is sending a read message and loading the file from the opened dialog window. Do you have any suggestion what could it be?
I'll have to investigate further. It may be that you'll have to distribute the files with the device.
That is the plan, but it doesn't load, only when I open a dialog window and read it manually, but that's not an option in this case.
where are you placing the files? can you send an example of how you are doing the reading?
I managed to make it work with this code if the file is in the same folder as the amxd.
Although I still cannot compile them. I mean did it, by dropping the files into the project thingy and saying copy to project folder. Is it what I need to do, yeah? Although I'm not sure how the code stays in the object, because it's empty when I open the patch up, that's why I need to read it from the path.
Yes distributing the shader file with the device is a requirement I believe. Don't think there are any other ways currently. Glad you found a solution.