Upgrade to versions 3.1 and 7.1
Changes in the iUpdate updater
1.We have introduced new installation rules for the VC Redist 2017 – 2019 installer:
- After starting the updater (automatically after starting the program or as a result of a manual call by the user) the first step is to install the update (files with new products and patches are downloaded).
- After completing this phase, the updater checks the version of the VC Redist package in the registry.
- If the presence of the appropriate version of the VC Redist package is detected, the updater will simply end at this point – the user can proceed to work with the new version of the program.
- If the correct version of the VC Redist package is not detected in the registry, the updater will proceed with its installation, which may cause the computer to restart automatically. The user will be informed about this and asked if they want to continue the installation (if they decide to do so, they should close all files and applications to protect themselves against data loss).
- If the user agrees, the VC Redist package is installed, which may end with a restart of the computer (without warning to the user).
- After restarting the computer, you can start working with the latest version of the program.
Note: if you do not agree to restart your computer, the updater will exit without installing the new VC Redist package. In this situation, it will still be possible to start the program in the new version, but one of the new options of Render PRO will be unavailable (the “Noise Reduction” button in the “Path tracing” panel will be inactive, because this function requires the latest VC Redist package). In addition, the updater will keep asking you to resume installation to install the missing package.
2. We eliminated irregularities that occurred after running the updater from the shortcut in the Start menu (the program was copied to the folder .. \ SYSWOW61, there was a key error and information about the lack of the package).
Common changes for CAD Decor PRO, CAD Kitchens and CAD Decor programs
3. Changes in the interface:
- the “Export to DWG” icon moved from the list of pages in the right menu to the top bar;
- a new “Measure” icon on the top bar;
- new icons for page list management (“Move up”, “Move down”, “Group”, “Ungroup”);
- new popup menu for elements inserted by the user, also for connection symbols (after selecting the object a marker appears – a small circle, after clicking on which a range of available functions develops, including new options “Move to the top” and “Move to the bottom “) (Note: for some objects, the right-click menu was already available in the previous version – this is still the case for dimension line segments, regular table cells and table with cabinet data, floors and section lines).new options in the right menu: “Dock to paper” (appears after inserting or selecting text) and “View rotation angle” (available in the card editing mode for the pages “Technical drawing”, “Floor”, “Tiles”, “Cabinets” and “Worktops”).
4.We changed the way of constructing and modifying the list of pages in the documentation. Each page has an ordinal number. Subpages (sections, sections) no longer appear as sub-elements e.g. in relation to the technical drawing, but as successive, equivalent positions. They can be freely grouped using the new “Group” and “Ungroup” icons above the page list. The content of groups can be collapsed or expanded using the arrows next to their names. The newly created group has a default name (Group 1, Group 2 etc.), which you can change as you like. Groups do not have numbering, while the items they contain are numbered in the order in which the entire list was displayed. We’ve added the option to change the names “Wall projection” and “Section” – in the previous version this was not possible. The order of pages and groups is no longer dependent on their name, as was the case earlier (e.g., A occurred before B, and the pages were automatically reloaded after the name was changed). At the same time, we have prevented the use of the “drag and drop” method to change the position of items on the list – now you should use the mentioned icons. The mouse is only used to mark the selected item – by clicking the left button (to select several in turn, you must additionally hold down the Shift key, and if you want to mark items that are not adjacent to each other on the list, use the Ctrl key while selecting subsequent pages).
5. In the card editing mode, we’ve added the ability to rotate the entire projection for those pages in the documentation on which the drawing is presented from above (except for single top views). The rotation of the projection is therefore not available for layouts and sections. Apart from the project view, some objects added by the user (own shapes, dimensions) are rotated outside of the project view, loaded from the CAD environment. Texts, references, tables, pictures as well as level and beginning markers for tiles do not rotate, so these elements are best applied after the projection rotation.
6. New tool: measuring. It helps in arranging objects relative to each other, e.g. placing all views at an equal distance from the left edge of the page. It is available under the new icon on the top bar in card mode and in scene mode. The measuring point’s starting point is in the upper left corner. The current location of the cursor is indicated by coordinates that are displayed in the lower left corner (refer to the distance units on the sheet).
7. New editing function: the ability to change the order of mutual covering of objects, i.e. moving elements to the top and bottom, depending on current needs. The options “Move to the top” and “Move to the bottom” are available in the popup menu for each element inserted by the user. Each newly added object is inserted on top. The project view, loaded from the CAD environment and elements of the title page, do not move vertically and will always be under the objects added by the user.
8. The new “Dock to paper” function, available for text fields in the “Element properties” panel in the right menu – thanks to it you can prevent their unwanted moving or even escaping from the working area when changing the scale.
9. We have added positioning lines for connections and symbols on sections and cross-sections.
10. The logo added to the project data will be remembered (unless the user removes it from the previously indicated location).
11. We have made available a new type of line – a dot (multi-point) line.
12. We have made it possible to rotate any number of elements visible on a given documentation page in a horizontal plane. These can be various objects (e.g. inserted shapes, pictures, notes, tables, as well as interior design elements in the design). Select them with the left mouse button (while holding down the Ctrl key), and then use the orange arrow (left-click and hold it, setting the rotation angle using the mouse movement – after setting the objects in the desired position, release the button).
13. At the request of users (90% of the answer to YES in our survey, presented at meetings with designers in the first half of 2019), we have allowed the possibility of moving and rotating objects loaded from the CAD environment (this does not apply to structural elements, i.e. walls and inserted in them doors, windows, recess, holes and protrusion, as well as any elements, i.e. platforms, plinths, 3D text, etc.). Changing the location of equipment elements is independent of the design, it does not entail any changes in the CAD environment.
14. We have added the option to restore default settings in the “Project settings” window (new “Restore default settings” icon).
15. We have enabled hatching used in the documentation when exporting to DWG format. The hatches are vector generated, making the image in PDF more accurate.
16. We have made available new printing formats – currently sizes from A0 to A5 are available, and we have added the “Line thickness factor” option in the “Export to PDF” window. This functionality allows you to change proportionally all lines in the project, so that it can become clearer after exporting to PDF and printing.
17. We have improved the visibility of table edges with cabinet data on PDF printout.
18. We have repaired the PDF export operation in the display of the project name (the “Project” entry appeared on the first export, and only the actual project name on the second).
19. We secured documentation against leakage of information about texts, as a result of which the program did not have data on the font type, which resulted in the fact that after generating the PDF file there were no visible dimensions. Now in this situation, the program will default to the default Arial font everywhere, which will guarantee the correct generation of dimensions and other texts in the documentation.
20. We have removed a bug that caused the preview to always be set on the first page of the documentation when printing or saving to the current page of the documentation instead of the page that was currently open.
21. We corrected the operation of exporting to PDF (large-scale drawings did not generate, and objects such as polylines and other figures, drawn by the user, always generated, even if all or part of them were outside the drawing boundaries and on the documentation some were cut off).
22. We have improved the appearance of objects that contain a lot of details in the PDF file generated in the documentation. The improvement was achieved by standardizing the width of lines displayed in the documentation and in the PDF file.
23. We have improved the display of stroke lines. However, it should be remembered that sometimes the original line thicknesses will be visible in the correct scale only after printing (on a sheet of paper), because in Adobe Reader their display depends on scaling (after enlarging the page, the line becomes thinner or thicker, depending on how will arrange the pixels). In addition, PDF files do not have a smooth transition between black and white (which occurs in the documentation module, which makes the lines appear more expressive.
24. We have introduced a correction to generate PDF from documentation to prevent the layout of texts from being changed in relation to the original.
25. We eliminated discrepancies between the visibility of objects in the documentation module and the resulting PDF file: there were differences in the display of texts and lack of consistency in the presentation of walls that overlap the platforms (the appearance of the hatching in the PDF file did not coincide with the appearance of the page in the program).
26. We’ve improved the validation of the file name given when exporting documentation to PDF (errors occurred if the project name had slashes: \ or /).
27. We have improved the generation of platform contours with arches with high density division (the problem was visible after generating the layout using two points, indicated on the bottom edge of the large platform, in the top view).
28. We have improved the operation of the drawing boundaries (workspace) so that they no longer respond to the click itself – it was treated by the program as a change in the workspace and resulted in rebuilding all existing layouts. Currently, the program will react in this way only to the actual shift of the work area (using the “drag and drop” method).
29. We have improved the display of the vertical slider (scroll) in the “Page properties” panel in the right menu, which also appeared unnecessarily when the panel was fully expanded and all options were visible. Currently, the slider is displayed only when the panel is reduced and any of the options will no longer be visible.
30. We changed the program operation so that each newly added object appears on top of the drawing. To place it under other objects, you can use the up and down panning options available in the popup menu. This solution removed the problems reported by users: it is not possible to add your own shape in the previously inserted photo and hide the added link under the table it concerned.
31. We secured documentation in the event of exceeding the RAM limit on your computer.
32. We’ve added protection against inserting copied objects on pages with a different scale at a very large distance from the project (off page). In the new version, if the pasted object (or group of objects) fits on the landing page, it will appear in the same place where it was on the source page. If the pasted objects do not fit on the page, the scale is changed so that they are all visible (in this case the message “The scale has changed so that the object will fit on the page” appears).
33. We prevented the occurrence of errors when, after copying an object, the user created a new page and deleted the page where the original object was located.
34. We have eliminated the situation where on the second attempt to export the documentation to DWG format the file extension did not appear in the save window.
35. Since saving the new documentation in a project in which the documentation was previously created results in the loss of the previous version (only one version of the documentation may exist for one project), we have added a message that warns about this. It appears when you try to start creating new documentation in a project that previously saved the documentation. The previous version is replaced with the new one when you save changes to the new document.
36. We have restored the proper functioning of the auxiliary line offset “from the object” – it should work only if the dimension line is outside the room, and the program incorrectly displayed the offset also for landings that were in the room.
37. The program was protected against a situation where markers and legend were not present on the floor plan.
38. The error causing the warning about the size of the cell to appear when starting the documentation has been resolved.
39. We made sure that the objects keep their order vertically if they are removed and then restored (they appeared in such circumstances on top, even if they were located on the bottom before removal).
40. We adapted the text field to display the Courier New font, and also corrected the display of the “Double click to type text” tooltip, because with the selected Courier font size 12 it did not fit in the default frame of the text field.
41. We have enabled the module name, which is visible on the top bar, to be translated into other languages. Until now, we used the image here, and now it is text, so it will translate in all supported language versions.
42. We secured the program against spontaneous renaming of pages in the page list when deleting other pages.
43. We’ve improved the performance of the fast dimension line for arbitrary shapes. A rectangular outline is determined for them and a fast line catches points on this contour, i.e. the border points on the model. In the case of arc elements, in addition to points on the contour, the line caught previously unnecessary additional points.
44. We improved the performance of the fast dimension line when zooming in and out (it was catching inappropriate points at the time), and we also changed the color of the dots visible at the intersection of the dimension line with elements to orange to improve their visibility.
45. We have secured the program against accidentally leaving an empty field in the tile legend in place of the tile name – if the user deletes the content and does not provide a new one, the field content (tile name from the database) will be automatically restored.
46. We corrected the program’s operation in naming examples created on pages that are copies of other documentation pages.
47. We’ve improved the undo behavior on pages created as copies of other documentation pages.
48. We have accelerated the refreshing of typed multiline text, which was particularly slow in very large projects (currently refreshing is performed from time to time, not after every entered or removed character).
49. We have corrected the display of shapes drawn by the user after the next launch of the documentation (previously there were additional points on them that made editing difficult).
50. We have secured the program from suspending the icad.exe process after opening the documentation twice, successively, containing automatically generated blocks (without closing the visualization in the meantime).
51. We introduced an correction thanks to which the program stopped asking about saving changes in a situation when the user only opened a project in which he had previously generated examples for the technical drawing, without making any changes.
52. We secured a situation where the user changed the wall parameters from paint to colour and back (the texture ID then got the value 0 incorrectly), which resulted in the lack of paint texture on these walls in the documentation and the absence of the paint legend.
53. We secured the program against losing the “Include drawing borders” option (earlier the cross placed next to this option disappeared after approving changes in the documentation and did not appear after re-opening the documentation, although the function was working and the drawing boundaries were taken into account).
54. We have unified the rules of font settings. Currently, if the “Descriptive Font” option (i.e. the font type) is changed in the settings, the change will apply to all text objects (except the dimension line for which there are separate settings). However, if the “Description font size” options are changed (i.e. size, bold or italics), the modification will apply to all objects except: title on the title page, table of contents header, contents of table of contents and legends (for these objects the size can be changed in the properties object after clicking on it). The settings will be remembered and transferred when creating the next objects of the given type.
55. We secured the program against unexpected errors, which sometimes accompanied the change of names of layouts.
56. We’ve made a slight visual correction in the name entry field for the new template in the documentation creation window.
57. We’ve corrected the function of replacing an object with a symbol – previously there were active options in the “Element properties” panel, which no longer applied to the symbol, and after selecting the symbol function again, it was no longer possible to undo this operation.
58. We secured the documentation against disturbances (blurring of the view) that occurred when the “Depth of Field” function was working. Currently, if this feature is active at the time the documentation is started, it is automatically turned off.
59. We have introduced changes in the alignment of text in links so that the aligned text does not get stuck and does not run off the page.
60. We have improved the refresh of the page thumbnail (view of the projection for which the layout was created), which appears in the lower right corner of each layout. Currently, new elements that will be added to the plan view load correctly, and the name of the layout on the thumbnail updates if the user changes it.
61. We secured the documentation against an unexpected error that occurred when copying pages after selecting the ‘Section’ option.
62. We’ve improved the operation of the table hider (hidden tables spontaneously returned to their place after switching to another page and returning to the one on which the table was hidden).
63. We have improved the appearance of circles and arcs with a large line thickness.
64. We have widened the display range of hints (hints) for options in the context menu of objects (tables, dimensions, inserted text fields, references, etc.). Until now, the hints appeared only after moving the cursor to the center of the button (after placing the cursor at the edge of the button they were not displayed). The tooltip display range now covers the entire button area.
65. We have accelerated the display of tooltips (hints) for icons, so that checking what they are used for will become more convenient and smoother, which is especially important for icons without inscriptions, which in the documentation are in the top, left and popup menus. Currently, hints appear after 0.2 seconds.
66. We’ve improved the display of the button to switch the drawing direction of a regular dimension line from vertical to horizontal and vice versa (you can change it using the Tab key).
67. We have secured the use of the Enter key in the documentation so that it does not recall the last function used.
68. We have blocked the option to enter an empty group name in the page list. Currently, if a user attempts to approve an empty field while editing a group name, the previous group name will appear (e.g., default “Group 1”).
69. We’ve corrected the undo operation of deleting an object underneath another object – after being restored it was on top instead of underneath.
70. We secured the program against the occurrence of the “Abnormal program termination” error, which occurred when exiting the program after running the export of documentation to PDF and canceling this operation.
71. We have adjusted the operation of snap points in the documentation so that they are superior to the active ORTHO option, as it is in the CAD environment.
72. We blocked the option of copying the title of a page after loading the saved documentation, because this situation is not foreseen and was accompanied by irregularities.
73. We have resolved the issue of “Error loading 27456 Tgr Socket” loading documentation.
74. We removed the red tag (red-green cross) that appears in a random position when the selected item is “gripped” to move it, and disappears when the move is complete.
75. We have added a context menu for symbols inserted by the user (after clicking on the object a small circular marker appears, after clicking on which the menu opens).
76. We’ve improved the text-matching behavior of the field (before, if the text field was in contact with the margin, the text after matching ran out of range).
77. We have corrected the function of changing the name of the section to avoid the appearance of entries with duplicate markings (eg Section A-A-A-A).
78. Starting from version 3.0 and 7.0 we have enabled changing the settings for each layer of the model separately – in the “Selected” tab, “Material Properties” panel in the right visualization menu. As a result, it became possible to hide selected fragments of objects (e.g. flowers in a vase, faucet by the bathtub or TV stand, which became unnecessary when placed on the wall). Therefore, by responding to the demand reported by users, we made it possible to remember hiding a fragment of the model after restarting the program. In addition, after generating the documentation, hidden objects or parts of them will be omitted (i.e. the documentation takes into account the state of the project from the visualization, not from the CAD environment).
79. We have introduced a camera rotation correction after choosing the “Select element” function.
80. We have improved the selection of the position on the halogen list when the “N” button has been enabled, which is responsible for displaying the numbering of halogen in the list and in the project, and also prevented the button from disappearing after removing the halogen group.
81. To avoid a situation in which a series of views rendered using Path Tracing will not be saved (this happened if the “3D Presentation” mode was set in the visualization save window when rendering of many views), we have introduced a mechanism that automatically changes the visualization save mode on “Path tracing” after running this render and file format from 3DE to JPG.
82. We have introduced an automatic change of the visualization saving mode when the “3DE Presentation” mode is selected when the visualization save window is closed. In the previous version of the program, if in this situation the user selected the “Quick save” icon, this resulted in not saving the file (this icon is only for saving image files, not three-dimensional presentations). Currently, we have used automatic switching from “3DE Presentation” mode to “Normal image” if the user selects the Radiosity algorithm in the “Render” panel and “Path tracing” mode after selecting Path tracing. In the case of customers who do not have the Render PRO module, the recording mode will switch to “Normal image” in a similar situation. Thanks to this, after selecting the “Quick save” icon, the appropriate illustrations will always be saved.
83. We secured saving changes when the only changes to the project were modifications to the list of lights (e.g. adding a new group). In the past, the program did not ask whether to save changes to groups and names of lights, because they were saved automatically when closing the visualization window.
84. We made it possible to translate the names of groups of lights in projects created on one language and launched in another (as the names of the groups of lights can be edited, the program treated them all – including default names – as given by the user, and therefore not subject to translation).
85. We’ve added the option of deselecting a group of lights using the Ctrl button. After clicking on a group item, it is marked in its entirety (all halogens included in it are selected) and to unselect it, you have to click on a single halogen item, inside or outside the group (this is intended). However, in response to user demand, we have added the option to uncheck a group – to do this, simultaneously select Ctrl on the keyboard and click the group position with the left mouse button.
86. We restored the correct segregation of halogens on the list after first adding them to the group and then removing the group – they remained at the end of the list, even if other items had a higher ordinal number (the list sorted correctly only after restarting the visualization).
87. Hiding and showing halogen in the project has been improved using the “Meshes” icon. Until now, hiding or showing halogen, which changed visibility, followed only after closing and re-opening the visualization. Now the change in the scene occurs directly after clicking on “Eye”.
88. We have repaired the display of previously hidden halogen (the hidden halogen did not appear again if the lights were turned on using F1 before attempting to hide it).
89. The program was protected against unexpected closing after selecting the shortcut (Ctrl + Z) after the sequence of actions in the visualization (applying tiles to the walls, replacing tiles, selecting the wall and clicking on the name of the group or manufacturer in the right menu).
90. We blocked the option of clicking the “Save” button in the visualization save window when generating an image or 3DE presentation (double-clicking too quickly resulted in unexpected errors).
91. We have introduced saving settings options available in the “Visualization Record” window for stereo images and post-process filters. Until now, only the basic settings (recording mode and format, resolution) and proprietary mark options were remembered – the others were reset when the visualization save window was closed, as a result of which it was not possible to use them using the “Quick save” function (which saves the view according to with the last settings in the visualization save window).
92. We secured the program against rotating the texture on the pedestal and floor of the built-in wardrobe by 90 degrees, which followed the lighting of the lights or calculations of the render.
93. We have prevented copying of wardrobes, as this is not a foreseen action, and in exceptional cases the wardrobe was partially copied using the “Copy” or “Mirror” option. However, there were irregularities, e.g. lack of equipment and textures present in the original wardrobe. In order to insert more than one built-in wardrobe in a project, you must create it yourself in the Wardrobes module.
94. We have improved the edition of halogens with their own IES styles assigned (created by the user himself or downloaded from the Internet). Earlier, when attempting to edit, such a light source ceased to glow.
95. We’ve added “IES” markings for halogens for which the user has loaded their own IES files (created by themselves or downloaded from the Internet). Earlier, this note appeared only for halogens, for which IES was chosen from the list provided by us.
96. We prevented the temporary appearance of a small square visualization preview in the lower left corner of the viewfinder, which replaced the camera view after selecting the “Depth of focus” function and moving the “Blur” or “Distance” sliders.
97. We’ve improved the display of views in the visualization (views were incorrectly assigned to icons, e.g. instead of the right view the project front was presented).
98. The linear view, available in the visualization under the L key, in versions 3.0 and 7.0 ceased to be visible after moving the camera. However, the function did not turn off, because in order to resume it, it was necessary to select the L key twice. We have restored the previous operation, in which turning off the linear view required selecting the L button, and not moving the camera.
99. We blocked the possibility of moving the visualization window, which appeared after clicking in a small area in the upper left corner and caused difficulties with closing the visualization (the top bar was hiding).
100. We ensured proper generation of the edges of the holes in the partition walls (earlier if there was a window or door in the partition wall and a niche or hole, the program did not create the edge of the hole and there was a gap between the walls.
101. We have corrected the movement in the visualization using the mouse (there was a problem when the cursor was moved outside the scene preview, on the menu bars – the image rotated spontaneously without pressing the left mouse button by the user). In addition, we have expanded the possibility of moving the camera (right mouse button option) and scaling (under the middle mouse button) – can now also occur after moving the mouse outside the stage.
102. We have improved the display of the project list in the project selection window, introducing protection against projects skipping to other positions when loading the list.
103. The sorting of projects in the project selection window after the modification date has been improved – the latest file is now displayed by default at the top of the list, which makes it easier to search quickly.
104. We have improved the display of the context menu for columns in the tabular view in the project selection window (after enabling or disabling column visibility in the table with the list of projects, the context menu with project options automatically appeared).
105. We prevented the program from crashing when the user right-clicks on the project list when opening the project before it is fully displayed (the program was stuck, it was not possible to select any option, and the popup menu remained on the screen until all files were loaded) projects).
106. We secured the program against the possibility of creating project save directories with an incorrect path.
107. We have secured the program against a situation in which a customer enters codes into a security key other than the one currently plugged into the computer’s USB port, or when he provides codes to an older version of the program. Previously, such codes were incorrectly recognized as valid, but the program could not start. Currently, the customer is informed about the mistake and can correct it himself.
108. We have solved the problem of deleting projects that occurred when deleting the contents of the entire project directory, consisting of leaving the p3dold files in the directory. Currently, all files are deleted correctly. At the same time, it is worth noting that the catalog itself will not be removed, but only emptied from project files. By the way, the limit of project display in the project selection window has been lifted – it used to be 2000 projects, currently there is no upper limit.
109. We’ve unified the font size used in the popup menu in the project selection window.
110. We have protected the program against the situation when the user gives a new project a name identical to the name of an already existing project and adds a space at the end. In an earlier version, a new project was created, but there were problems saving it using the shortcut (Ctrl + S). Currently, the program will not allow you to create a new file – it will behave as if there was no space at the end, which is analogous to the behavior of Windows, which trims spaces at the end and beginning of the name.
111. We corrected the program operation at the stage of creating a new project in a situation where the name of the subdirectory contained a space at the end or only spaces in the name (this resulted in errors and creating a project called “Drawing.dwg”).
112. We have secured the program against a situation when an attempt is made to create a project whose name consists of only spaces – the program will behave as if the name was not given at all, it will not allow the file to be created.
113. We have completed the translation of the window that appears when exporting a project from the list in the project selection window (the heading “Enter archive name” instead of Polish text appeared on it).
114. We added the Polish translation in the “Status” table in the project selection window (instead of “Program is too old” now appears “Project from a newer version of the program”). We have also corrected the information about the unassigned database.
115. We unified and refreshed the appearance of various elements of the “Project selection” window – we now use the same font everywhere: Segoe UI, which is compatible with the Windows 10 standard), we also changed the nomenclature so that the project was called “project” everywhere (and not ” document “), we removed the outdated icon in the upper left corner of the window and aligned the top menu layout.
116. We have secured the program against the inability to save the project using the “Save as” option when a non-printed Unit Separator – ASCII 31 character is present in the name (it is currently being automatically deleted).
117. We secured the program against a situation in which some code from fields 2 to 7 was removed from the “Coding” window. The program saved empty fields. Only after deleting text from the first or last field did the user receive a message saying that the code was incorrect. Currently, regardless of which field is missing text, the user will be notified.
118. We refreshed the appearance and content of the “Help” window in the program: new graphics appeared and the appearance of the code field was changed – identical to the “Coding” window.
119. We changed the size of previews generated by the Converter when adding objects to the user base (from 100 × 100 to 400 × 400 pixels, i.e. to the standard used in our databases).
120. We have secured the Converter against an error that occurs when the file being added came from a folder with a name containing special characters. Currently, either the file will be loaded or a message will appear informing you of the reason for the failure (the presence of special characters in the file path).
WALL CREATOR AND EDITOR
121. In response to user feedback regarding the insufficient visibility of previews of doors, windows, ledges, recesses and openings, which resulted from the small size of the wall element editing window, we have added a new preview panel that opens at the top of the screen after moving to the ” Windows and doors “and” Extras “when inserting wall elements. It is also activated by the “Insert window or door” and “Insert additional element” buttons in the Wall Editor.
122. We have eliminated the case in which the “Insert” button in the wall elements editing window became inactive after the next opening, if the window was previously closed using the “Close” button. After reopening, information about the element indicated for insertion was lost and it was necessary to find it again in the list to be able to insert it into the project – at present this information is remembered.
123. We have solved the problem that after editing a recess or projection created in the visualization during which a collision with another element occurred, the element was removed from the CAD environment. Currently, if the collision change is canceled, the item will not disappear, but will return to its original settings.
124. We have unified the maximum available room height in the Wall Maker (50 m) and Wall Editor (20 m) – currently 50 meters everywhere. In addition, in the Wall Editor window we have introduced a direct automatic value correction if the user enters a value exceeding the maximum (as is the case in Wall Creator).
125. We secured fields in the Wall Creator, used to define parameters for inserting windows and standard doors, against the possibility of entering negative values (which were neglected by the program, as a result of which the elements were inserted in the same way as in the case of positive values, which could have been misleading). Currently, when you try to enter an unacceptable character, a warning message appears and the character does not insert.
126. In both modules we changed the font to Segoe UI.
127. We blocked the possibility of changing the colour for walls and other elements drawn by default (e.g. floors, worktops, kitchen cabinets). Currently, when inserting or editing (e.g. modifying the room layout in the Wall Editor), their colour is always taken from the layer. This ensures colour stability for these objects, regardless of what drawing colour you choose. Earlier, if the user changed the colour of the drawing tools, and then, e.g., edited the wall, then after modification the walls were inserted in the colour that was selected for drawing.
128. We have repaired the operation of protrusions and recesses of varying thickness or depth, lying on one wall – the dimensions of the element that was inserted as second were aligned with the dimensions of the first.
129. We have used a new solution in case of entering incorrect parameters for windows or doors (e.g. negative values or exceeding the wall dimensions) – now the program will change the entered value to the correct one and automatically recalculate other values related to the given wall.
130. We secured the program against a situation when it incorrectly recognized the chamfer added to the partition wall as non-adjacent and prevented the use of the “Adjust wall” option (also for the immediately selected support wall the adhesion settings did not return to the correct settings).
131. We have implemented in the application code the information required for it to start with the appropriate card (GeForce).
132. Changing the font in the hider to Segoe UI.
INSERTING INTERIOR ELEMENTS
133. Changing the font in the add-on.dll module to Segoe UI.
INSERTING ANY ELEMENTS
134. Changing the font in the add-on.dll module to Segoe UI.
135. Changing the font in the slupy.dll module to Segoe UI.
Changes in programs with the Render PRO module
136. We have blocked the possibility of applying material to walls while rendering, while dragging the material or using the “Bucket” if it would require rebuilding the area (the following message will appear: “Changing the material requires modification of the area. Therefore it is not possible during rendering.”) .
137. We have adjusted the autosave behavior in the visualization by checking that render is not turned on when it starts. In this situation, the autosave will start only after the render calculations are completed.
138. We blocked the Undo/Redo option during Path tracing and Radiosity calculations to avoid errors that could have been associated with undo or redo operations while the render was running (e.g., incorrectly recalculating areas where a operation again, the type of cladding changed, e.g. from texture to tile).
139. We have developed support for larger projects than before to export them to the obserVeR application (however, too large projects may not load).
140. We have deactivated the “Spherical panorama” option when rendering multiple views to protect the program against errors. The option to create a spherical panorama is therefore only available when rendering a single view using the “Current view” option.
141. We have improved the depth of field visibility for visualizations created using the Path tracing algorithm.
142. We have achieved a significant acceleration of rendering performance as a result of rebuilding the kernel of the rendering system. Thanks to the adoption of new technical solutions in large projects, the Path tracing algorithm works up to 200% faster than in the previous version. This applies even to such arrangements in which curtains or other translucent elements were used, which so far have often not achieved a satisfactory appearance.) The first phase – the calculation of GI, or global lighting, has been reduced by several dozen percent. The change in the calculation technique is also accompanied by a change in the display of partial Path tracing results – if the program detects that the user has moved away from the computer (based on the lack of mouse movement), then it will display the partial results less often, thanks to which the time of obtaining the final result will be even shorter.
143. The new “Hum Reduction” tool for the Path tracing algorithm. It significantly improves the appearance of illustrations obtained by this method in a very short time. Three levels of noise reduction are available – 50, 100 and 200 samples. Selecting one of these options automatically changes the number of samples analyzed by the Path tracing algorithm. For example, after selecting “200”, the number of analyzed samples will be set to 200, and after reaching this level, the program will apply a noise suppression algorithm that will smooth the image in places where it was imperfect (reduce graininess). Thanks to this, the obtained results will have many times better quality than it would result from the given number of samples.
144. New option for the Path tracing algorithm in the “Colour tones” panel in the left menu: “Colour saturation”. At the minimum slider setting the image will become monochrome, at the maximum – the colours will be strongly saturated. This function is useful when the colours become unnaturally intense after increasing the contrast – you can then reduce the colour saturation to make the visualization look more realistic.
145. New function in the ‘Material properties’ tab in the right menu: ‘Thin glass’. It allows you to get a natural look of thin-walled glass for any objects with given transparency and reflection properties (minimum 1%). They can also be models that at the stage of drawing were not adapted to properly present the properties of the glass, i.e. drawn from one wall. After using this option, they are interpreted by the rendering engine as if they had a minimum thickness (two sides), which is necessary for the natural appearance of the glass. Any object, such as a glass sphere, without using this function will look like a solid, and when you select the “Thin glass” option – as if it were empty inside.
146. New White-Filmic filter added at the end of the filter list in the “Path tracing” panel. Strongly brightens the scene and at the same time reduces the contrast, shifting the range of shades of gray. It is worth using it when you want to get very bright scenes, such as using the “Exposure” parameter, but at the same time avoid overexposure (when using the “Standard” filter, with high “Exposure” places strongly illuminated do not look favorable, because they light up too much).
147. Another difference from the previous version of Render PRO is that the partially reflective materials are brighter, so that white objects that have been reflected are no longer darkened.
148. We have fixed the switching on or off of the transparency of the walls, which did not work properly after switching on the lights with the F1 key.
149. We’ve solved the problem causing the program to spontaneously turn off when trying to turn on the lights in the visualization.
150. We have improved the “Quick save” option, which saves the view with the settings that the user recently left in the “Visualization save” window. There were complications if the user set the recording mode suitable for direct lights or the Radiosity render, and after closing the visualization save window, he used the Path tracing algorithm, which requires a different save mode. In the new version, the recording mode will automatically switch to “Path tracing” and the appropriate illustration will be created on the disk after using the “Quick write” function. Also in the opposite situation – that is, when the “Path tracing” mode is set in the recording window and the user starts Radiosity calculations, the illustration saving mode will automatically switch to the appropriate one (the mode changes when the “START” button is selected). In addition, when the Radiosity algorithm is selected in the “Render” tab, the “Path tracing” mode will be grayed out in the visualization save window, as it does not apply to this method of calculating global scene lighting.
151. We unblocked the Ray tracing algorithm when, after performing Radiosity calculations, the lights were switched on with the F1 key, and then Final gathering was started – after finishing the calculation the “Ray tracing” button should be active, and this did not happen, the option was unavailable.
152. The error of previewing the previous view during the Path tracing calculations has stopped.
153. We have removed a bug that meant that in order to change the halogen color, you had to edit it twice and set the color (it did not load the first time).
154. We introduced a block of the Ray tracing function after changing the parameters of lights, because there were problems with its conversion at that time. Currently, after modifying the lights, the button deactivates – in order for it to become active, you need to re-calculate Radiosity.
155. We have eliminated the problem of displaying the correct preview of the effects of Path tracing, which occurred if Radiosity calculations were made before, then switched to Path tracing and changed any option in the “Color tone” panel, without performing Path tracing calculations.
156. We have solved the problems regarding the export of the project to the obserVeR application after the change of the texture on the wall, which was made after the Radiosity calculations. Currently, if the user performs such an action, the “Project export” button will become inactive until Radiosity calculations are performed again.
157. We adjusted the operation of hiding and displaying elements when using Path Tracing, as well as refreshing the camera position on the recalculated view (if previously hidden elements were discovered after calculations, then after restarting Path Tracing remained invisible in the results view, and if after calculations, the camera and light direction were changed with the F1 key, then hidden elements were discovered, the view in the preview did not update).
158. We corrected the operation of the Final gathering function, which hung under the discovery of elements and prevented restarting the Radiosity algorithm – it was necessary to exit and re-enter the visualization.
159. Using the Final gathering function uncovered hidden elements after performing Radiosity calculations – we protected the program against this error by deactivating Final gathering when the user hides the element (s) after completing Radiosity calculations.
160. In the current version of render, the bump mapping effect is equally well visible in visualizations obtained using the Radiosity algorithm, as well as Path tracing (in the past, after applying Path tracing it was less pronounced).
161. We’ve eliminated a memory leak and spontaneous termination of the renderprocess.exe process following the replacement in a CAD environment of a model that was previously rendered using Path tracing (by deleting the object and inserting the new one in the same place instead of using the “Edit” or “Change”).
162. We have eliminated the differences in scene lighting that occurred between the effect after lighting the lights with the F1 button and the situation when one of the objects was selected and its properties were changed (before the distortions disappeared, it was necessary to restart the visualization).
163. We blocked the launch of Final gathering during Radiosity calculations, which was possible after the resumption of the latter, and should not have taken place.
164. Turning on the lights using F1 after calculations Ray tracing blocked the possibility of recalculations (the “START” button stopped being active) – we’ve removed the fault.
165. We’ve improved the render path tracing behavior so that it does not omit tangent surfaces when calculating (e.g. wall and ceiling contact, wall and other wall, wall and free element, etc.). Thanks to this, they will now be properly lit. The problem was associated with the optimization of the algorithm in the calculation of lighting of elements with small surfaces, e.g. stucco.
166. We protected the program from displaying the error “There was a problem with rendering (…)” when two graphics cards are running.
Changes in programs with the Ceramic Tiles Design Module
167. We solved the problem with duplicate items in the tile legend (there were separate, identical items for each tile strip that could not be removed). At the moment, the names of the tiles in the legends do not duplicate.
168. We changed the appearance of the cursor on the page with tiles, because until now it was gray and blended with the background, if the design included gray tiles. Currently, the cursor is two-coloured (a black cross with a white border), thanks to which it will always be visible, regardless of the background colour.
169. We’ve improved the performance of normal maps in tile databases.
170. We secured the program against an unexpected error occurring when applying tiles to the floor (after closing the error message and restarting the visualization, the project was not visible – until the program was restarted).
171. We secured the program against the disappearance of tile images in a freshly added collection in the user database that followed the clicking over between collections.
172. We eliminated the error that occurred after clicking on the name of the group or manufacturer in the right visualization menu after performing the previously specified actions with tiles (the message “There is no such tile in the database anymore” appeared).
173. We removed the “sqrt: DOMAIN error” error that occurred when defining tile layouts, which was due to the fact that the “Layout Preview” button was incorrectly active even before the second vector was defined (it was possible to call the preview of the layout before completing the determination of both vectors, which resulted in an error).
174. We’ve improved the “Preview System” button because it remained inactive after defining both vectors.
175. Another improvement in the operation of creating tile layouts – we have secured the program against an unexpected error that appears after selecting the “Layout preview” button.
176. We have adjusted the shifting operation when, after activating the function and selecting the point based on which the area will be shifted, the operation will be canceled by selecting the Escape key. The next time the shifting function was selected, the area was automatically marked and the operation was interrupted.
Changes in programs with the Ceramic Tiles Design Module with the Tile Base Editor
177. We have updated the link to the price list on our website for people who will try to run the Tile Base Editor module without the registration code (information about the lack of code and redirection to the current page appears – a 404 error appeared earlier).
178. We have secured the Tile Database Editor against errors that occur when a user attempts to add an 8-bit pixel image to their tile database. Until now, the Editor only responded to the 24-bit format, and now it is possible to add an image with an 8-bit format.
179. We unified the reflection settings ranges for tiles in the Tile Base Editor and visualization. Until now, the range of these settings in the Editor was different to the range available in the visualization. In the Editor, you could set reflections from 0 to 100, and in the visualization from 0 to 255. Therefore, the tile for which the reflection was set at 70% in the Editor, had a property of 27% in the visualization. It will now also have a bounce slider set to 70%. This will facilitate the mirror tiles effect. In addition, we changed the name of the option in the Editor from “Gloss” to “Reflections”, because it is responsible for reflections, not gloss (in the past we used a different nomenclature).
Changes in CAD Decor PRO and CAD Decor programs
180. We have improved the deactivation of tiling functions (e.g. displaying a label with information about the tile, operations in the areas covered with tiles, etc.) to avoid errors associated with running documentation from the level of visualization.
181. We verified the default lighting for previews of created tile layouts, because the colours, in particular very light tiles, were distorted (they looked much darker than they actually were).
182. We secured the tiling module against incorrect application of tiles in a size different than those found in the database, in the case of repeated editing of the areas covered with tiles.
183. We eliminated the incorrect display of a removed tile arrangement on the wall when moving the area that was present if another arrangement was already applied to the wall, and then the operation was canceled.
184. We have secured the program against an error that caused the front surface to be unintentionally removed while moving tiles on the wall in some circumstances.
185. We prevented the program from skipping millimeter values to prevent situations where the depth of the recesses and protrusions created from the level of the tiling function would be rounded to full centimeters.
186. We eliminated the problem that caused the substitution of various tile arrangements, combined with undoing, to cause tiles to mix on the wall.
187. We removed the mistake where changing the tile layout to another one on which the joint was previously defined would restore the default joint.
188. The distance option in visualization worked differently on the walls and floor – after changing in both cases, this option applies to the tops of the tiles.
189. We have introduced a correction in calculating the number of hexagonal tiles in the tile list. Hexagons now calculate just like ordinary tiles priced into pieces. This means that the program counts whole and trimmed tiles, but these tiles are not optimized. After selecting the position with the hexagons in the list, the program also shows tiles trimmed and whole.
Changes in CAD Decor PRO and CAD Kitchens programs
190. We have improved the display of the new set after replacing the kitchen furniture set in the visualization, in a situation where before the replacement and after the set replacement Path tracing was started and calculations were interrupted in their initial phase (in the earlier version, after lighting up the cabinets from the previous set appeared).
191. We have added a designation regarding the type of selected object, visible in the right menu on the “Layer” tab next to the model name for objects such as household appliances, kitchen furniture, worktops, windows and doors. Until now, only the model name appeared there, i.e. most often its code. Currently, these entries have the format “Household Appliances – CN 136241 X” or “Cabinet – B60-060 / 96_1”.
192. We have improved the import of kitchen designs, created on a base, not present in the system (unnecessarily duplicate messages appeared and there were problems with the valuation).
193. We introduced security for a situation in which the lack of a standard render refresh after replacing sets caused the “SQRT Domain error” error and the program to shut down.
194. We have improved the run of the quote if the project was imported into a program in which the furniture base on which it was made is not present.
195. We have removed a problem where some models from the FRANKE database could be inserted into a project only once in a given program session.
196. We changed the font in the module to Segoe UI.
197. We removed access to the option of table top generation, which was incorrect for single table top views generated from the level of the top table top (for each generated table top the “Generate” button was active and its selection resulted in the creation of another table top view, with an empty table).
198. To prevent errors with the automatic generation of skirting boards that occurred when there were no skirting elements in the kitchen furniture base used, or only some, e.g. top and wall skirting, and there were no stickers or bottom skirting (e.g. in Delinia 2019 base) , we used two solutions: in the absence of slat elements, the generation option will be unavailable, while when only some elements are present, the loading of colors for absent objects will be blocked.
199. The “Slats” window has two tabs: “Autogeneration” (with options for automatic generation of slat elements) and “Drawing slats” (with options for their manual application). The option of automatic generation of labels was, however, available in the “Drawing slats” tab, and not in the “Autogeneration” tab (after selecting “Label” from the drop-down list, and then clicking on a specific label on the list, the “Generation” button appeared). As this is an automated function, we decided to move
200. Go to the “Auto-generation ” tab. We have added a check-box there: “stickers”, after selecting which a new tab appears in the left part of the window, in which you can select the sticker for automatic generation.
201. We added detection of partition walls when inserting upper and lower slats on hanging cabinets (previously strips were unnecessarily applied on the edges adjacent to the walls).
202. We changed the font in the module to Segoe UI.
203. We have fixed the problem with the valuation of cabinets, whose fronts had several layers – in addition to the DOOR layer, FILLING and EDGE (this is the case with fronts of different colours, for example). We have removed the problem with highlighting the position of such cabinets in the red quote. In addition, the quote will now display all body and front colours, as long as the layers in the cabinet are not different than the standard ones or the user does not change the colour to his own in the visualization. In addition, the names of textures in the visualization and the valuation are updated accordingly after being replaced in the visualization.
204. We changed the font in the module to Segoe UI.
USER CABINET EDITOR
205. We have implemented in the module code the information required to use the appropriate graphics card (GeForce).
206. Minor correction of messages regarding the removal of grip diagrams and the module version.
207. Change the font in the valuation to Segoe UI
208. Changing the font in the blaty.dll module to Segoe UI.
Changes specific to CAD Kitchens program
209. While working in CAD Kitchens program, if it hung and the user directed the cursor to its position on the taskbar, a window with the words “CAD Decor” was displayed. The entry was changed to “CAD Kitchens” and the old icon was updated, also visible in this window.
iUPDATE.exe 188.8.131.52 15.01.2020
demo_Maciej_Danczura (.dwg .p3d .dat) 15.01.2020
demo_Marek_Myszkowski (.dwg .p3d .dat) 15.01.2020
Model1.dll-Model9.dll 184.108.40.206 05.12.2019
kafle.dll 220.127.116.11 15.01.2020
CADDecor.exe 3.0.7314.41003 10.01.2020
CADKuchnie.exe 7.0.7314.40966 10.01.2020
CADDecorPro.exe 3.0.7314.41015 10.01.2020
Manager.dll 18.104.22.1680 09.01.2020
Editor.exe 22.214.171.124 08.01.2020
wycena.dll 126.96.36.1993 02.01.2020
ukrywacz.dll 188.8.131.52 18.12.2019
agd.dll 184.108.40.206 13.12.2019
listwy.dll 7.0.7286.35954 13.12.2019
szafki_nowe.dll 220.127.116.11 10.12.2019
konwerter3d.dll 18.104.22.168 06.12.2019
baseedit.dll 22.214.171.124 06.12.2019
slupy.dll 3.0.7279.32630 06.12.2019
blaty.dll 126.96.36.199 04.12.2019
walls2.dll 188.8.131.52 28.11.2019
podesty2.dll 184.108.40.206 27.11.2019
Walls_dll.dll 220.127.116.11 27.11.2019
RenderDll.dll 18.104.22.168 22.08.2019