February 1, 2017, 4:42 am
Author:
jendore
Posted: Wed Feb 01, 2017 1:42 pm (GMT+1)
| laszlonagy wrote: |
I will report this GRAPHISOFT. It seems from the error message that the CineRender module experiences the crash, not the core ARCHICAD program.
Curious. In any case, they will know what to do about it. |
Hi Laszlo
Thank you for sending on the details. Did you hear anything back from GRAPHISOFT? I have had no contact from them myself.
_________________
Windows 10 Pro (64 bit)
Dell Precision T1700
AMD FirePro V4900 (FireGL V) 1.0 GB
Archicad 20
↧
February 1, 2017, 5:04 am
Author:
David Maudlin
Posted: Wed Feb 01, 2017 2:04 pm (GMT+1)
Zosia:
Since your error message mentions "calculating split polygons", it could be that shadow generation is the problem. Go to the Elevation Settings > Model Display > Sun and Shadows > and uncheck "Sun Shadow". You should also look through this dialog box to see if there are other elements to disable.
David
_________________
David Maudlin / Architect
www.davidmaudlin.com
Digital Architecture
AC20 USA+MEP •
iMac 27" 4.0GHz Quad-core i7 | 24 gb ram •
MacBook Pro 2.5GHz | 16 gb ram •
OSX10.10.5
↧
↧
February 1, 2017, 11:39 am
Author:
Kassandra
Posted: Wed Feb 01, 2017 8:39 pm (GMT+1)
Thank you, I thought it looked like something GPU-related. However everything is updated and did hardware test showed nothing wrong. I'm going to try running Archicad 20 and see if its a similar issue there.
_________________
Archicad 19 Educational Version // Macbook Pro Early 2015 Retina, i5 2,7 GHz, 8GB ram // macOS Sierra
↧
February 1, 2017, 4:22 pm
Author:
Barry Kelly
Posted: Thu Feb 02, 2017 1:22 am (GMT+1)
I had a similar problem on a PC but it was the 3D window that went white (sometimes black).
The model was still there - you just couldn't se it but could select it.
I am not sure if it is related but this PC had a GeForce graphics card and was running a program called "GeForce Experience".
I deleted that program and all was fine again.
Barry.
_________________
Versions 6.5 to 20
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bit
↧
February 2, 2017, 6:13 am
Author:
Zosia
Posted: Thu Feb 02, 2017 3:13 pm (GMT+1)
Thank you to both of you! I will try to follow your advices. I will let u know if I menage to do it ...Thank u!!!
_________________
Zosia S.
------------------------------------
i7-6700K CPU @ 4.00 GHz -16 GB RAM
34" LG 34U98 (3400x1400), GeForce 1080
SSD+HDD, Win10 PRO 64 Bits (US)
AC19-AC20 (64-bit, latest build)
-------------------------------------
↧
↧
February 2, 2017, 6:13 am
Author:
Zosia
Posted: Thu Feb 02, 2017 3:13 pm (GMT+1)
Thank you to both of you! I will try to follow your advices. I will let u know if I menage to do it ...Thank u!!!
_________________
Zosia S.
------------------------------------
i7-6700K CPU @ 4.00 GHz -16 GB RAM
34" LG 34U98 (3400x1400), GeForce 1080
SSD+HDD, Win10 PRO 64 Bits (US)
AC19-AC20 (64-bit, latest build)
-------------------------------------
↧
February 2, 2017, 7:23 am
Author:
Eric Batte
Posted: Thu Feb 02, 2017 4:23 pm (GMT+1)
I've been testing file operations over SMB from our Macs. Speed is slow at best. Usually about half as fast as AFP. What garbage!
I've tried adjusting server-side and client-side settings advertised online to improve speed from Mac clients, but nothing really helps.
I've even tried various SMB servers, including my Mac server, Freenas, various other linux distros and it's consistently slow. Apparently Apple has deprecated AFP in lieu of SMB without actually making it work.
_________________
Eric
MacBook Pro (Retina, Mid 2012), 8 GB RAM, Mac OS 10.11.3, 27" Thunderbolt Display
↧
February 2, 2017, 1:24 pm
Author:
Eric Batte
Posted: Thu Feb 02, 2017 10:24 pm (GMT+1)
Just for grins, here are the results of SMB vs AFP test. I'd like to see if others could post their results here, too.
1. Open a Terminal Window and type rsync --stats --progress
2. Next, drag a large file (larger is better) from Finder to the Terminal window. This will drop the path of your source file into the command.
3. Finally, drag-and-drop a folder on your server to the Terminal window to drop the destination path of your SMB server
4. Press Return to execute. Note the results.
5. Repeat steps 1-4 except change the destination path to a folder on your AFP server.
In my results below you can see that the file copied over SMB at 28.25 MB/s while the same file copied over AFP at 50.19 MB/s - nearly twice as fast.
| Code: |
eric:~ ebatte$ rsync --stats --progress /Users/ebatte/Desktop/16-895.235.T\ -\ Lively\ Exploration\ 16-895.235.pla /Volumes/Shared\ Folders/Projects
16-895.235.T - Lively Exploration 16-895.235.pla
83875888 100% 28.25MB/s 0:00:02 (xfer#1, to-check=0/1)
Number of files: 1
Number of files transferred: 1
Total file size: 83875888 bytes
Total transferred file size: 83875888 bytes
Literal data: 83875888 bytes
Matched data: 0 bytes
File list size: 67
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 83886253
Total bytes received: 42
sent 83886253 bytes received 42 bytes 23967512.86 bytes/sec
total size is 83875888 speedup is 1.00
eric:~ ebatte$ rsync --stats --progress /Users/ebatte/Desktop/16-895.235.T\ -\ Lively\ Exploration\ 16-895.235.pla /Volumes/Shared\ Folders-1/Projects
16-895.235.T - Lively Exploration 16-895.235.pla
83875888 100% 50.19MB/s 0:00:01 (xfer#1, to-check=0/1)
Number of files: 1
Number of files transferred: 1
Total file size: 83875888 bytes
Total transferred file size: 83875888 bytes
Literal data: 83875888 bytes
Matched data: 0 bytes
File list size: 67
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 83886253
Total bytes received: 42
sent 83886253 bytes received 42 bytes 33554518.00 bytes/sec
total size is 83875888 speedup is 1.00
eric:~ ebatte$ |
FYI, server in my test is a MacOS Sierra Server running both SMB and AFP.
_________________
Eric
MacBook Pro (Retina, Mid 2012), 8 GB RAM, Mac OS 10.11.3, 27" Thunderbolt Display
↧
February 3, 2017, 6:07 am
Author:
Beka Gujejiani
Posted: Fri Feb 03, 2017 3:07 pm (GMT+1)
Hello, guys!
After updating to macOS Sierra my Archicad 20 worked fine. But at some point, when I was trying to render a model it just froze. I force quit and sent a bug report but the problem is the same after restarting.
It's the same for all models. It's the same after reinstalling archicad. It's the same after even REINSTALLING macOS Sierra.
It freezes when I start rendering or try to preview the rendering.
I fear it has maybe something to do with my graphics card?
Additional info: Internal rendering engine works just fine.
Can you help out with any suggestions?
↧
↧
February 3, 2017, 7:42 am
Author:
ejrolon
Posted: Fri Feb 03, 2017 4:42 pm (GMT+1)
Check that your render settings DO NOT have Grass turned on. Looks like one of the rendering presets (Exterior Medium Physical) has the setting on by default and that will slow down any computer to the point that it looks like C4D is frozen.
_________________
eduardo roló
n AIA
MBPr 2.6 i7 16GB ram, MacPro dual quad 2.8 18GB ram
OS X 10.XX latest
AC20US -> AC08
↧
February 6, 2017, 8:56 am
Author:
Beka Gujejiani
Posted: Mon Feb 06, 2017 5:56 pm (GMT+1)
Thank you for your reply.
There's no grass material in the scene that I'm trying to render. It's nothing but a wall. Do you think it still may be causing the freeze? I'm gonna try anyway this evening. Thank you
↧
February 6, 2017, 10:11 am
Author:
Beka Gujejiani
Posted: Mon Feb 06, 2017 7:11 pm (GMT+1)
Ok, I've tried your solution. It doesn't work but it has changed something - now it did render but took 4:30 minutes just to render a single column. I tested the same scene with internal render engine and it took 3 seconds with highest quality. Any more suggestions?
↧
February 6, 2017, 10:36 pm
↧
↧
February 7, 2017, 9:50 am
Author:
dorebe
Posted: Tue Feb 07, 2017 6:50 pm (GMT+1)
I believe I have the same problem, fractions show fine in the schedule, but come up as ? in the view ports.
↧
February 7, 2017, 9:52 am
Author:
dorebe
Posted: Tue Feb 07, 2017 6:52 pm (GMT+1)
I believe I have the same problem, fractions show fine in the schedule, but come up as ? in the view ports.
↧
February 8, 2017, 8:49 am
Author:
Riven
Posted: Wed Feb 08, 2017 5:49 pm (GMT+1)
Hi all,
Has the following occurred for others in AC20 yet?
The act of selecting a single hotlink module produces a 'spinning wheel' loading time, and freezes AC20 for a moment. Selecting more hotlink modules, takes longer, and can keep AC20 frozen for minutes. Selecting all hotlink modules & objects (Ctrl+A hotkey command) in model space can freeze AC20 indefinitely. Why was this not a factor/problem in AC19 for the same project files? -The same actions would not cause such significant slow-downs.
Some relevant project info, and machine info for consideration:
- AC 20 v4020
- Teamwork Project LAN BIM Server (114MB on server)
- 80,000 SF single story project, Hotlink Modules represent a single unit, (about 600-1000SF)
- "Element Information" palette closed
- Favorites palette is closed
- Teamwork palette; Organizer, renovation filter, trace palettes are open
- Trace turned off
- showing layers of objects consisting of only walls
- No other active AC20 instances running
- no active user programs running
- Windows 7 Pro x64
- 16GB RAM
- Intel Core i7-4790K @ 4.0GHz (quad-core)
- Intel SSD 240GB drive
Any feedback would be appreciated. Thank you!
↧
February 9, 2017, 4:50 am
Author:
KatalinBorszeki
Posted: Thu Feb 09, 2017 1:50 pm (GMT+1)
Hi All, yes, this is a bug!
We have recorded it. Thanks for letting us know!
best, k
_________________
Katalin Borszeki
Implementation Specialist
GRAPHISOFT
http://helpcenter.graphisoft.com - the ArchiCAD knowledge base
↧
↧
February 9, 2017, 8:20 am
↧
February 9, 2017, 7:01 am
Author:
danvandyk
Posted: Thu Feb 09, 2017 4:01 pm (GMT+1)
I finally made an account for this forum because an Archicad feature has been ruining my day. This particular grievance pushed me over the edge.
Currently using Archicad 19. Noticed that a new(er) feature in this version is that [solid] fills are displayed on screen with a *grid* (wtf?!) pattern overlaid. In other words, I make a solid fill (25%) and when I look at it on my screen it has grid lines running through it. It doesn't print like this, it just shows up on the screen.
I know somebody probably added this feature with a flawed notion that it would help users.
Can somebody explain how to get rid of this garbage? I've had my principals hovering over my shoulder all day, commenting on an elevation, and they keep confusing these display features with actual joint placement. I am catching hell for something I can't control. Sometimes when I'm drafting I confuse these with real lines as well.
If there is no way to get rid of this feature, please direct me to the programmer who added it so I can strangle them. ![Evil or Very Mad]()
![Evil or Very Mad]()
![Evil or Very Mad]()
_________________
Who came up with this program? -Angry Intern
↧
February 9, 2017, 7:43 am
↧
