You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do not know, if this is the correct place to ask, but I give it a go nonetheless:
OS: Arch Linux x86_64 6.10.10-arch1-1
maxima Version: 5.47.0
wxmaxima Version: 24.08.0_DevelopmentSnapshot
gnuplot Version: 6.0 patchlevel 1
(using Wayland)
When using wxplot3d I get the following error and a blank color:
set pm3d hidden3d 100 border lw 0.5 lt rgb "#000000"
^
"/tmp/maxout19174.gnuplot" line 10: invalid pm3d option
Plotting it with 'plot3d' works, even though an error is still shown.
Researching on Sourceforge (maxima) I found that someone encountered the same bug, but it has been said to have been patched. If anyone has an idea what might be the error, I'd be happy.
The text was updated successfully, but these errors were encountered:
leafina2895
changed the title
Error while using plot3d
Error while using wxplot3d
Sep 30, 2024
The issue was fixed by Gunter Königsmann (thanks!) - on 2024-05-11. And you are using Gnuplot 6 and Maxima 5.47.0 (released in June 2023). No Maxima release was made after the solution from Gunter.
Either use a Maxima development version (Git) - or an older Gnuplot version.
Interestingly plotting seems to work outside of wxMaxima without any problems.
It still sends the error message, but plots it in a different window anyways. (Still using Gnuplot 6 and Maxima 5.47.0)
Plotting in 2d works either way.
I do not know, if this is the correct place to ask, but I give it a go nonetheless:
OS: Arch Linux x86_64 6.10.10-arch1-1
maxima Version: 5.47.0
wxmaxima Version: 24.08.0_DevelopmentSnapshot
gnuplot Version: 6.0 patchlevel 1
(using Wayland)
When using wxplot3d I get the following error and a blank color:
Plotting it with 'plot3d' works, even though an error is still shown.
Researching on Sourceforge (maxima) I found that someone encountered the same bug, but it has been said to have been patched. If anyone has an idea what might be the error, I'd be happy.
The text was updated successfully, but these errors were encountered: