FreeCAD|
|
Wall Error Messages.PNG (210,222 bytes) Wall opened with v16.PNG (38,946 bytes) Wall opened with v17-7745.PNG (40,950 bytes) Wall Python Console.PNG (104,794 bytes) Wall v16 opened with v17-7745.PNG (41,797 bytes) Wall v16 opened with v17-13508.PNG (30,323 bytes) |
|
|
Per the enormous sticky at the top of this page: First post to forum to verify [their] issue and also discuss with the community |
|
|
I did post it to the forum. See "Creating wall freezes 3D view" under the Arch forum. It appears the issue 0003430 is having the same or similar problem. |
|
|
The platform stated above at the beginning is incorrect. It should be a PC 32bit running Windows 10 32bit. |
|
|
@dgingrey Edit: took care pasting the forum thread. |
|
|
Forum thread: https://forum.freecadweb.org/viewtopic.php?f=23&t=27862 |
|
|
Under additional information I ment to say I did not have any problems when using the 32bit v0.17.13508 on a windows 10 64 bit machine. |
|
|
My assumption that this problem occurs on machines running Windows 10 32 bit was incorrect. I upgrade to Windows 10 64 bit and the error still occurs. Also I have observed on the machines where the error occurs that during the start up of FreeCad v17 on the initialization screen "Mod\Measure\Initgui.py not found" appears. I do not get this warning during start up on machines which run Freecad v17 correctly. I see that issue 0003478 is reporting a similar error. |
|
|
INITGUI NOT FOUND.PNG (251,327 bytes) |
|
|
Here is the initialization screen showing the initgui.py file not found. This shows up only on installations which produce the error when creating a wall. I don't know if it has anything to do with the error. |
|
|
@yorik please advise |
|
|
These are stange errors. I don't think they are related to 0003478 / 0003430 because the UI is in english here... The "Mod\Measure\Initgui.py not found" could indicate that FreeCAD wasn't properly installed. Not sure what to do, I can't reproduce the problem on my machine, and I haven't seen other windows users with the same problem yet... |
|
|
@dgingrey can you reproduce bug with a bleeding edge 0.18dev version ( https://github.com/FreeCAD/FreeCAD/releases/tag/0.18_pre ) and report back here... ? |
|
|
Rectangle v18.PNG (69,516 bytes) |
|
|
OS: Windows 10 Word size of OS: 32-bit Word size of FreeCAD: 32-bit Version: 0.18.13830 (Git) Build type: Release Branch: master Hash: 262d7c0cd05c6072d5807ebb98a0a3113cfebba0 Python version: 2.7.14 Qt version: 4.8.7 Coin version: 4.0.0a OCC version: 7.2.0 Locale: English/UnitedStates (en_US) I can reproduce the error using FreeCad v0.18.13830 on a 64 bit machine running windows 10 32 bit. I will try on a 64 bit machine running windows 10 64 bit and also on a 32 bit machine running windows 10 32 bit and report back. Wall from rectangle v18.PNG (76,452 bytes) |
|
|
OS: Windows 10 Word size of OS: 32-bit Word size of FreeCAD: 32-bit Version: 0.18.13870 (Git) Build type: Release Branch: master Hash: f0964a9c052ee666631cd9caec1655790964ecb6 Python version: 2.7.14 Qt version: 4.8.7 Coin version: 4.0.0a OCC version: 7.2.0 Locale: English/UnitedStates (en_US) I installed V18 on a 64 bit machine running Windows 32 bit and also on a 64 bit machine running Windows 64 bit and got the same results. An error occurs when creating a wall and the 3D view freezes up. It is only the 3D view that is affected. The rest of the screen seems to be unaffected. The combo view can be manipulated. I can make changes in the combo view but they do not show up in the 3D view. It seems the changes are being applied. For instance if I change the end point of the line I created the wall from and then delete the wall in the combo view the 3D view is unfrozen and the changes to the line now show up in the 3D view. |
|
|
OS: Windows 10 Word size of OS: 32-bit Word size of FreeCAD: 32-bit Version: 0.17.13528 (Git) Build type: Release Branch: releases/FreeCAD-0-17 Hash: 5c3f7bf8ec51e2c7187789f7edba71a7aa82a88b Python version: 2.7.14 Qt version: 4.8.7 Coin version: 4.0.0a OCC version: 7.2.0 Locale: English/UnitedStates (en_US) OS: Windows 10 Word size of OS: 32-bit Word size of FreeCAD: 32-bit Version: 0.18.14426 (Git) Build type: Release Branch: master Hash: 3927a2ed8b009ab4dfdca53fbebf0060193b67b4 Python version: 2.7.14 Qt version: 4.8.7 Coin version: 4.0.0a OCC version: 7.2.0 Locale: English/UnitedStates (en_US) I just tried the latest versions of FreeCad v17 and V18 and got the same results. |
|
|
I just discovered that I cannot print the any drawing on any machines which produce the above error when trying to form a wall. I don't know if this related to this same error or not. When I try and print the drawing the print preview is blank and so is the resulting printout. When I print from a machine that does not produce the error when forming a wall I get the correct print preview and resulting printout. Angle Bracket.PNG (15,705 bytes) Angle Bracket Print Preview blank.PNG (19,906 bytes) Angle Bracket Print Preview.PNG (72,083 bytes) |
|
|
Using version 0.18.15417 the error message has changed. It now reads Unhandled Base::Exception caught in GUIApplication::notify. The error message is: Access violation when trying to form a wall from a d-wire. Does anyone know what this means? |
|
|
Assigning to 0.18 release in hopes this ticket will get addressed before 0.18. |
|
|
Still don't know what we can do, all the reported operations work fine for me... @dgingrey can you please post precise step-by-step instructions of what I should do on my computer to reproduce your problem? |
|
|
OS: Windows 10 Word size of OS: 32-bit Word size of FreeCAD: 32-bit Version: 0.18.15860 (Git) Build type: Release Branch: master Hash: 3b708c7f84b0425076b520e1d95627b20fd75fe0 Python version: 2.7.14 Qt version: 4.8.7 Coin version: 4.0.0a OCC version: 7.2.0 Locale: English/UnitedStates (en_US) To reproduce the error I draw a line, rectangle using the draft tools or sketcher tools and then select it and press the wall button. The 3D view freezes up. The same thing happens when using the wall button to construct a wall from scratch. The wall trace shows up in the 3D view and then the view freezes up. If I delete the wall then the 3D view functions correctly again. This error started to occur after version 17.7745 I have also noticed that on machines that produce this error I cannot print any drawing. The print preview and printout are always blank. |
|
|
No problem following these steps for me.. The weird thing is that many windows 10 users are using the arch tools, nobody got such problem either.. Are you by chance using FreeCAD in another language than english? |
|
|
I have made some headway on this issue. I have been able to reproduce this error on five different machines. Each of the machines is set up for a duel boot configuration to boot up into either Windows 7 or Windows 10. On all the machines the wall forming error did not occur when booted to Windows 7 but did when booted to Windows 10. On four of the machines I could not print the 3D view under Windows 7 or Windows 10, the print preview, print out and export to PDF where all blank, however drawings produced using the drawing workbench could be printed. I suspected the video display driver might be causing the problem since the version under Windows 10 was different than under Windows 7 on each machine. I tried replacing the driver under Windows 10 with the driver for Windows 7 and the wall producing error was corrected on all the machines when booted to Windows 10. On one of the machines this also corrected the printing problem however on three of the machines I still cannot print the 3D view. Any suggestions on solving this? |
|
|
Is this problem still present with a 0.19 version from https://github.com/FreeCAD/FreeCAD/releases ? |
|
|
Using the following version OS: Windows 10 (10.0) Word size of OS: 64-bit Word size of FreeCAD: 64-bit Version: 0.19.22988 (Git) Build type: Release Branch: master Hash: cdc01cb20cfa74079c45b9dc2dab81e3248b2aa5 Python version: 3.6.8 Qt version: 5.12.1 Coin version: 4.0.0a OCC version: 7.3.0 Locale: English/United States (en_US) I did not have this problem. I was able to construct a wall from a d-wire or sketch. |
|
|
I guess we can close this issue then. Thanks a lot for testing again! |
- Anonymous
