Recently, I tried to run LFS on a machine with an Nvidia card and it seems that anti-aliasing (or whatever) is not working when rendering shadows.
I tried to mess around with Program Settings in NVIDIA Control Panel and pretty much only setting the Gamma correction off makes it a bit better but it's still ugly compared to AMD.
Here is an example - check the shadow under the bridge:
Offtopic a bit: What kind of analyzer are you guys talking about? I thought the analyzer at lfsworld.net/rafa was turned off along with the Remote since the ddos party. Because rafa only shows a blank page for me, just like Remote
Right.
So it seems your LFSLazy.exe is not actually in C:\Users\user\Downloads folder. So the exec command is giving the parameter error when it's trying to execute that exe file while it's not there.
If your LFSLazy.exe is in the same folder as LFS.exe - replace /exec "C:\Users\user\Downloads\LFSLazy.exe" with /exec ".\LFSLazy.exe"
if it's not in the same folder - you need to specify the whole path so for example if your LFSLazy.exe path is C:\LFSLazy\LFSLazy.exe then replace /exec "C:\Users\user\Downloads\LFSLazy.exe" with /exec "C:\LFSLazy\LFSLazy.exe"
BTW you don't really need that second start_LFSLazy.lfs script file. You can use just the autoexec file to start Lazy. So it would look like this:
// This script is run when LFS reaches the main entry screen // You can use it for initialisations, running scripts, etc.
Just go to C:\LFS\data\script folder, open autoexec.lfs in Notepad, copy the text from the 6th line and paste it here.
Hard to help you without seeing what's in there.
Or you could just delete the autoexec file, but I don't recommend doing that because you would have to start Lazy manually every time you start LFS. And that would be silly.
Edit: I bet it says /run start_LFSLazy so also copy text from line 2 from start_LFSLazy.lfs file and paste here.
Just open autoexec.lfs in Notepad or some text editor, and check the 6th line.
There is something wrong with the text in that line. Same for start_LFSLazy.lfs.
It probably contains a command that for some reason doesn't work.
Maybe just copy the text from those files here so we can see what's wrong with it.
Just wondering why does your script folder contain a custom .lfs script while you don't even understand what it does. Did someone else send you his LFS folder?
Hi you!
That means parameter at line 2 in C:\LFS\data\script\start_LFSLazy.lfs and parameter at line 6 in C:\LFS\data\script\autoexec.lfs are not valid
Not sure why you use additional script to start Lazy. I only use autoexec.lfs with line
/exec ".\LFSLazy.exe"
and it works fine (if LFSLazy.exe is in same folder as LFS.exe).
What about having LFS trigger the Copy action again right after you place a copied (not cut) object? That way the object would still be visible.
Not seeing exactly where you are placing an object will be a bit annoying I can imagine.
Though I like that you can change color of an object before placing it without changing color of one that is already placed.
Edit:
Oops, I just realized the nonsense in that suggestion. That it would also deselect the placed object..
What about a Duplicate function then? Ctrl+D is free