Search the Community
Showing results for tags 'image'.
Found 10 results
-
Hi! I try to upload an avatar pic from my PC, it's within the 100x100 limit, it's not bigger than 5 KB and I still get this error: The total filespace required to upload all the attached files is greater than your per post or global limit. Please reduce the number of attachments or the size of the attachments. Any idea why?
-
Does anyone else seem to have image problems? For example I might insert an image via "Insert Image with URL" function, and it works ok; but a couple of days later, it just becomes a weird, unclickable link. Example here: Could mods look into this? Thanks!
-
Greetings,LPub3D 2.0.14 is released. LPub3D is an Open Source WYSIWYG editing application for creating LEGO style digital building instructions. It uses the LDraw parts library, the most comprehensive library of digital Open Source LEGO parts available and reads the LDraw LDR and MPD model file formats. LPub3D is available for free under the GNU Public License v3 and works on the Windows Operating Systems. Portions of LPub3D are based on LPUB© 2007-2009 Kevin Clague, LeoCAD© 2015 Leonardo Zide.and additional third party components. LPub3D can run under POSIX-compliant operating systems, such as Linux, Mac OSX, & BSD using WINE HQ. You can download from sourceforge.net or check for updates in your existing installation. LPub3D 2.0.14.838.2 Features and enhancements ------------ Fix: File reload after external source change breaks page drop-down combo dialogue(r837) * When a file is reloaded after being changed by an external source, the drop-down menu for selecting a page doesn't work until after navigating using another method. Fix: Image orientation does not conform when page orientation changed to Landscape (r836) * Image generation was not inheriting the proper page size values. Fix: Extra characters "%3" in margin meta and page size meta does not display the page size identifier(r835) * Oops, allocated the page size identifier variable to the wrong meta - should have been allocated to page size meta instead of units meta (units meta is used for setting the margin). Consequently, the page size meta is missing the size identifier (A4, Letter, etc...) because the place-holder to pass the variable is not there. This must have happened during the patch process from the maintenance branch because it did not present during my tests. Both issues are now corrected. Cheers,
-
Greetings, LPub3D 2.0.13 is released. You can download from sourceforge.net or check for updates in your existing installation. Interesting fixes are the ability to switch part occurrence (times used) in the PLI between per step and per submodel on called out and submodel pages; the ability to insert one-to-many non-faded models (e.g. with alternate attachments/views etc...) when fade step is on; and new meta for pages size including the standard identifier - e.g. A4, Letter, Legal etc... and print/export performance improvements. LPub3D 2.0.13.834.2 Features and enhancements ------------ Fix: Logging options added to Preferences (r832) * Select logged attributes and logging levels. Fix: Prompt search directory settings reset (r831) * Prompt to inform that the search directories have been reset after the search directory reset button is clicked. Restarting LPub3D is not required. Also changed menu items "Reset 3D Viewer Model Cache" to "Change Temp File Cache" and "Reset Image and Model Caches" to "Reset All Caches". Fix: Inconsistency between part counts in submodels and part counts in call-outs where multiple instances are involved (r829) * For submodels, the PLI part counts reflect only one instance of the submodel, even if multiple instances are used in the same step. The instance count is correct, and the BOM has the correct total number of parts. With this update, sub-model pages displaying instance count now have a context menu option to display parts per step/page or not (total parts consumed by the number of instances indicated. Previously, for callouts, you have the options (see context menu) to display parts list per callout (one instance) or not. When you select no parts list per callout, the PLI will show all the parts consumed by the total number of instances in the callout. If you choose parts list per callout, the PLI is moved to the callout and only the parts for a single occurrence of the callout is shown. The idea here is if you have 5 occurrences of the called out assembly, you'll need 5x the parts total, but only 1x parts are shown to indicate what you need to build an instance of the called out assembly. On sub-model pages displaying the instance count, there is only one behaviour for PLI counts (the most intuitive) which is to display the parts list per step. This is intuitive because the primary role of the PLI is to show what you'll need to build an occurrence of the step shown - it is not the intention to mimic the BoM. Nevertheless, I added a context menu item to not display parts list per step and instead display total parts consumed by the number of occurrences of the submodel in the parent submodel/step. Fix: Page size and orientation processing update (r826/833) * Further industrialization of the print/export module. This update streamlines the process and realizes some performance gains. There are some key changes. Notably, page orientation and page size are now mutually exclusive. This means when switching from Portrait to Landscape, accompanying the orientation meta with a transposed page size meta no longer required or managed. Here is an illustration: Previous behaviour when editing a page size change required the following meta commands: 0 STEP 0 LPUB PAGE ORIENTATION LOCAL LANDSCAPE 0 LPUB PAGE SIZE LOCAL 11.0000 8.5000 Note that the page width and height have been transposed. Going forward, transposition of the page width and height when switching from Portrait to Landscape is automatically managed by LPub3D. NOTE: This update is NOT backward compatable. An accompanying transposed page size meta to indicate the switch from portrait to landscape as shown above will be treated as a new page size meta for that page. Consequently, using this meta to 'switch' orientation will actually result in NOT switching the orientation as LPub3D will automatically switch again the switched page size meta. If the user is only interested in changing the orientation, the proper meta command going forward will be: 0 STEP 0 LPUB PAGE ORIENTATION LOCAL LANDSCAPE To help with accurately displaying the page size identifier in the setup and context menus, the standard page identifier is now appended to the page size meta command. For example: 0 LPUB PAGE SIZE 8.5000 14.0000 Legal 0 LPUB PAGE SIZE LOCAL 8.5000 11.0000 Letter 0 LPUB PAGE SIZE LOCAL 5.8000 8.3000 A5 0 LPUB PAGE SIZE LOCAL 5.8678 8.3456 Custom Along with the width and height values, if the page size is non-standard, the identifier "Custom" will be automatically used. Additionally if an identifier is not present, the identifier "Custom" will automatically used. The page identifier is displayed in the Page Setup dialogue and Size/Orientation change context menu dialogue. Also, the LPub3D print/export function no longer needs to parse the model file to capture, in advance, page sizes. This capture is performed during the existing page parse and load functions and is exposed to the print routines during printing/exporting. This change was necessary to better enable mixed-size page export/printing where it is necessary to 'look ahead' to get the next page's size and orientation parameters in order to configure the printer engine before processing the page. Fix: Expand INSERT MODEL meta command behaviour (r825) * When using part fading LPUb3D will now process multiple INSERT MODEL commands rendering the CSI content at each command. For example, if the instruction document includes different model attachments, the editor can now include a non-faded image of the entire model with each attachment. Here is an example of he proper command sequence when used in conjunction with BUFEXCHG: 0 BUFEXCHG B STORE 0 //... default model content... 0 STEP 0 BUFEXCHG B RETRIEVE 0 BUFEXCHG A STORE 1 0 445 -46 -10 1 0 0 0 1 0 0 0 1 attachment1.ldr 0 STEP 0 LPUB INSERT MODEL 0 LPUB INSERT PAGE 0 STEP 0 BUFEXCHG A RETRIEVE 1 0 0 0 0 1 0 0 0 1 0 0 0 1 attachment2.ldr 0 //STEP These last 3 lines are optional when editing the model file. 0 //LPUB INSERT MODEL If they don't exist and fade step is ON, they will be automatically created by LPub3D 0 //LPUB INSERT PAGE Fix: The PNG output of a model with various page orientations is not correct (r824) * Cleared page buffer before rendering each page. Also corrected a typo causing page range to sometimes not work for image exports. Cheers,
-
Hi, for those, who wants to link images from theirs Google Photos and to EB post, here is how to do it (I did not found any such post here, so I made it): (this is extract from this post ) At Google Photos resize your browser so image have desired size on screen click with right mouse button on image and choose: in Chrome: "Copy image URL" in Internet Explorer: "Copy" in Firefox: "Copy image location" [*]At Eurobricks post editor click on "Image" icon add "-tmp.jpg" at the end of URL. If you do not this, error "You are not allowed to use that image extension on this community. " will appear! That's all! As you can see bellow, same picture on Google Photos , different sizes here.
-
Hello Eurobrickers! I recently (Just today) made a recreation of the shot from the Rogue One Teaser of the Death Star Radar being inserted into position. Here is a look at the image: Now, while it is not absolutely perfect, keep in mind that I used 10143 which obviously limited me from getting the trench in the shot. However, I feel that it does the job pretty well for something that is just meant to look cool, not absolutely perfect. Now, all of this is CGI, none of it is from an actual picture of Lego. I used LDD and then worked that model into Maya, then After Effects for some touch ups.
-
Hey guys From time to time I use to play a bit with new rendering light setup for my renders and the latest one (basically still just a prototype of one of the next MOCs of mine) makes me a bit head ache as I am not sure which version - lighter or darker - looks more natural (in a way, of course)...please, tell me what do you think, what is your opinion (thanx in advance for any thoughts on these two)? BTW: I personally favor the lighter one but as I am using white background and there is a lot of white color bricks it may sometime become visibly bleeched at some spots of that color, so I really don't know: do you think it is too obvious (there for it would be better avoiding such version) or could I go with the lighter one anyway? Please, click images for FullHD versions so it is better visible... LIGHTER VERSION: DARKER VERSION:
-
I made a scanner
technical posted a topic in LEGO Technic, Mindstorms, Model Team and Scale Modeling
I made a scanner from the printer I made earlier. I drew a test page and also scanned a print I made on the same frame from when it was a printer... re-digitized. It uses the color sensor. The digitized image is saved to the EV3 memory where I can download it on the computer as shown in the last image below. It's pretty crude but it's a good proof-of-concept I could improve on. Anybody else done this? -
So here is something fun I came up with Someone will upload a simple image to this topic. Then the next person will change something in that image that was uploaded and upload it again. Then the next person will change the image the previous person uploaded and so on until the image looks nothing like the original. ]
-
here is the link I found it quite useful and no account is needed. http://imageupload.co.uk and it is FREE
.thumb.JPG.3c74c0d405dc1afb04b2fa216ebc79e6.JPG)
