-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
commandline output does not match gui output #614
Comments
Thank you for reporting this behaviour. Can you provide an example model file that produces this behaviour ? It would also be helpful if you can provide the LPub3D runtime log. Many thanks. Cheers, |
@trevorsandy why abandoned? what address can i send a model file to? |
Because I do not have enough information to reproduce this behaviour and I did not see any response to my request.
You can attach it to this ticket. From what you have written, the behaviour does not seem to be specific to a particular model file, unless you have demonstrated that the behaviour is as expected when using a generic model with the specified anit-cutoff commands. Alternatively, if you can simply provide the commands you are using and the model/submodel/callout etc... configuration that produces the behaviour, it would be enough - but a simplified sample model would be best. I will reopen the ticket as we are progressing. Cheers, |
@trevorsandy the model is copyrighted, please send an address i can mail it to, i can send the instruction file |
Ok, send it to [email protected]. If you are sending the complete file, please specify the exact step(s) in the file and the steps to reproduce the unexpected behaviour along with any relevant project setup and global preferences screenshots. Cheers, |
Subject
running instruction output via linux cli for a same model file with identical lpub instructions generates two different documents, namely, certain pages contain cutoffs that LPUB paramteres were set to avoid.
Running LPUB in gui mode corrects these issues.
See attached images:
Environment
The text was updated successfully, but these errors were encountered: