Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- archgary March 2016
saveFrame() with P3D
I've been using saveFrame for exporting images in 3D (P3D) since Processing 2.X. But the results of saveFrame with P3D in Processing keep giving me weird results (background changing, line overlapping...etc), like the attached images:
Is it because I am running in Windows 10 in high resolution? sound stupid, but this is really bothering me for a while. And I just keep going back to Processing 2.X for generating movies.
Thanks for anyone who answer the question in advance.
Tagged:
Answers
With same code, in Processing 2.X works perfectly fine as here:
Thanks for my Facebook friends, the export of processing, Frederik Vanhoutte, for the suggestions so that I found the solution. It seems to be the problem of graphic cards. If possible, try to choose the powerful graphic cards of your own laptop/computer. In my personal case, I am using Lenova Yoga 900 under Windows 10, with an Intel HD graphic card. The way I solved the problem is to modify the 3D settings of the graphic card, turn the Conservative Morphological Anti-aliasing(no idea what it is) into Override Application Settings, and it works perfectly fine now.