Menu
Logged-In As
ACCOUNTNot Logged In
Create an awesome screenshotBRL-CAD
Status: ClosedTime to complete:
48 hrs
Mentors: Sean
Everyone loves to see screenshots of software in action. We use screenshots in our marketing and outreach. See some of the examples below that we already have. Create an awesome screenshot of either mged or archer. It should be graphically interesting, show wireframe and/or raytraced geometry and give some sense of capability. References: |
Uploaded Work
| File name/URL | File size | Date submitted | |
|---|---|---|---|
| Screenshot from 2012-11-28 21:43:16.png | 140.3 KB | November 28 2012 19:43 UTC | |
| Screenshot from 2012-11-28 23:10:40.png | 452.9 KB | November 28 2012 21:38 UTC | |
| Screenshot from 2012-11-28 23:17:48.png | 476.3 KB | November 28 2012 21:38 UTC | |
| ScreenShots.zip | 1.4 MB | November 29 2012 22:07 UTC | |
| dxf.g | 498.1 KB | November 30 2012 16:44 UTC | |
| Screen Shot 2012-11-30 at 6.37.50 PM.png | 493.4 KB | November 30 2012 16:44 UTC | |
| Screen Shot 2012-11-30 at 6.45.00 PM.png | 505.0 KB | November 30 2012 16:45 UTC |
I would like to work on this task.
This task has been assigned to dmusan. You have 48 hours to complete this task, good luck!
Melange has detected that the initial deadline has passed and it has set the task status to ActionNeeded. The student has 24 hours to submit the work before the task is reopened and sent back to the pool for other students to claim.
The work on this task is ready to be reviewed.
While I like that you found an interesting model to import, it's not very easy to tell what either of those models are. I suggest a few changes:
If you only show one graphics window (the one on the left), that will leave room to include the command window, tree view, and raytrace control panel on the right. If you select the raytrace button on the raytrace control panel, it'll be a little easier to tell that it's a usb drive. You can play with the background and colors to make it look interesting.
One of the mentors has sent this task back for more work. Talk to the mentor(s) assigned to this task to satisfy the requirements needed to complete this task, submit your work again and mark the task as complete once you re-submit your work.
The deadline of the task has been extended with 1 days and 0 hours.
The work on this task is ready to be reviewed.
Thank you for your feedback.
I have send anther screenshot. Please tell me if it is okay now and if not what else I could do to improve it.
Thanks.
Heh, that guy looks kinda scary, no? It's visually interesting but we don't want to scare people away! How about something a little more mellow? I'm still thinking that the two graphics windows is just too much. Try opening up the tree view (Tools-Geometry Browser).
One of the mentors has sent this task back for more work. Talk to the mentor(s) assigned to this task to satisfy the requirements needed to complete this task, submit your work again and mark the task as complete once you re-submit your work.
Hi,
I have uploaded some more screenshots. Please let me know what you think.
Oh, the last one looks like something we can use, thanks!
By the way, did you about the raytrace or did it crash? I see the rr_refract output and that's not usual. If you try any of our other rendering tasks, you might want to try this on the command line:
rt -A0.75 -w1024 -n768 -c {set ambSamples=256} -c {set ambSlow=1} -F/dev/X -o image.png
the laptop screenshot you made would probably look particularly good rendered with those options
Last time the raytrace crashed. I think it was because my laptop couldn't handle it, but now I when I tried to raytrace it again it didn't work any more... and I also tried on anther computer, so I will upload the schreenshot as it is. I will also upload the .g file.
Thank you!
The work on this task is ready to be reviewed.
Congratulations, this task has been completed successfully.
We like reproducible crashes. We can investigate and fix those. Keep your .g file and instructions on how to get it to crash. We'll be uploading several new tasks that basically have you find and document a reproducible crash. Since you've done that, you'll be able to submit what your geometry with a set of steps that reproduces the crash.
As GCI comes to a close, we wanted to take the time to say THANK YOU for all your efforts. This comment interface closes after GCI is over, so you're encouraged to join our mailing list where we'll be announcing contributions from GCI participants like yourelf over the upcoming months:
https://lists.sourceforge.net/lists/listinfo/brlcad-news
If you've provided your full name, we'll be sure to credit you in our authorship documentation and you'll see your name in a future announcement. If you contact us at devs@brlcad.org or via IRC, we'll even let you know when your work is integrated and follow up with updates. You're welcome and encouraged to contact us any time, especially if you have a question about how to continue participating in Open Source after GCI is over, but even if just to keep in touch. Note that ongoing participation in Open Source is one of the most impressive skills to have on your resumé. Take care, be well, and thank you again!