It seems that DL5 beta 3 still has the incorrect path for ScreamerNet under OS X.
With LW 10, NewTek relocated and also renamed the ScreamerNet executable under OS X. It is now called ‘lwsn’ and resides in the ‘bin’ subfolder within the LW10 application folder.
I thought we had updated this path already, but obviously this is not the case. 
I’m downloading it right now so that we can check the path. We also just realized that they changed the path for the Windows version too. We’ll make sure the default path for both OS’s are correct for the beta 4 release.
Thanks!
The submission script for LW also seems to be MIA. Is this known?
It should be there. I just checked a fresh Mac repository install that was done using the beta 3 repository installer, and it’s where it should be:
/your/repository/clientSetup/Lightwave/SubmitToDeadline.ls
Maybe you’re looking for it in the submission folder? The LW submission script is currently the only script that doesn’t support the proxy/repository script setup, mainly because I could never figure out how to call one .ls script from another (there is no documentation describing how to do this). The clientSetup folder contains the scripts that need to be copied to the workstations, and in LW’s case, the clientSetup script is the full script.
Cheers,
Indeed - I was looking in the submission folder
I’ve had a query lodged regarding your LScript question. So far, no answer from NT.
One reply from the NT boards was :
–
I would guess they same way you call any other generic function in layout:
For example:
CommandInput(“Generic_add_emitter”);
I’m not sure if that is the answer you are looking for, though.
Thanks for the info. I’ll have to read up more on how @insert works.
Cheers,
@insert is, I think, only supported under LW10 with relative paths. It works to effectively inline insert the contents of the reference LScript file. @insert with absolute paths is available in earlier LW versions, but absolute paths are probably not ideal - the only solution would be to either store a preference, or deliver a compiled LScript that bundles everything into a single .lsc
Example real world usage is Passport, which was recently open-sourced by its developer :
sourceforge.net/projects/lw-passport/
with files at :
lw-passport.svn.sourceforge.net/ … -passport/
@insert is discussed here :
newtek.com/forums/showpost.php?p … stcount=71
That thread has some interesting LScript-related information, such as the cited line numbers not always being correct due to a long-standing LScript bug.
I took a look into this today, and a big problem is that the full path to the repository script needs to be hard coded in the proxy script. Usually, we have the proxy script figure out where the repository is and build the path to the script automatically.
So if we were to go this route, the person installing the proxy script would need to edit it after copying it to the workstations. If the path to the repository ever changes, each proxy script would have to be updated accordingly. I’m on the fence regarding whether this is acceptable or not…
Cheers,
Ping NT with your requirements. You have special access to them now, I think 
I’ve sent an email to LW support. I’ll let you know when I hear back.
Cheers,
Better is lw-features@newtek.com). Both of those drop your request in to their FogBugz-based tracking system. Just be aware that, if you submit this way, any report you make public displays links to any other reports from that same e-mail address.
To avoid this, you can also submit your request/report via their web-based system : secure.newtek.com/FogBugz/defau … ommand=new