Both fairly minor, but from what i can see, if one deliberately traps an error, e.g. in the case of your turntable animation script not having a render target selected, after dealing with it, the core lua process seems to trap it again. Or is it me?
2nd
@shortcut ctrl + 3, this works as a shortcut in windows, (@shortcut alt + w) and this (@shortcut ctrl + w) don't work. It appears that shortcuts with non numeric quilifiers might be broken.
beat
Mark
2 potential lua bugs
Windows 11, 2x Intel I9, 64GB Ram, 2x GTX 1080 TI, 1 x RTX 380 TI, Oculus Quest 2
- stratified
- Posts: 945
- Joined: Wed Aug 15, 2012 6:32 am
- Location: Auckland, New Zealand
Hi Mark,
You're right, we'll fix them for the next release.
cheers,
Thomas
You're right, we'll fix them for the next release.
cheers,
Thomas
If its the same issue, the double error messages bug has been there for a while - since 1.28 - I mentioned it on 26 Jan in the release testing thread.
i7-3820 @4.3Ghz | 24gb | Win7pro-64
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
We have fixed these double errors a couple of releases ago. The turntable, daylight, and regular time animation scripts are shipped with the more recent release candidates, they're the three items right below the "reload scripts" option in the script menu.
--
Roeland
--
Roeland
Can you tell me what you did so i can fix it in my own script.
thx
thx
Windows 11, 2x Intel I9, 64GB Ram, 2x GTX 1080 TI, 1 x RTX 380 TI, Oculus Quest 2
- stratified
- Posts: 945
- Joined: Wed Aug 15, 2012 6:32 am
- Location: Auckland, New Zealand
Hey Mark,MB wrote:Can you tell me what you did so i can fix it in my own script.
thx
This one is not really a bug in Octane, it's a consequense of how those scripts where written. There are 2 different "modes" to run a script in Octane:
- from the editor: output and errors are logged in the editor's output window
- from the menu: output is logged in the log window and errors are signaled via a popup
showError
(which you are using as well) was show a dialog (first annoying popup) and then error out (second annoying popup when running from the menu). What you can do is:- just error out and don't show the dialog
- show the dialog and return, it's then up to your script to make sure it checks return values correctly and returns at the top
cheers,
Thomas