<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Windows 10 April Update and DirectX/OpenGL issues in Installation &amp; update</title>
    <link>https://community.graphisoft.com/t5/Installation-update/Windows-10-April-Update-and-DirectX-OpenGL-issues/m-p/292217#M30111</link>
    <description>I have the same condition now.  Not sure where it is coming from.  I installed 22 RC and updated my Dongle, updated Windows, installed iCloud for Windows... all about the same time.  Checking for Updates with ArchiCAD said my dongle was out of date. Never seen that before.  Perhaps I should not have updated it.  &lt;BR /&gt;
&lt;BR /&gt;
Unitalled 22 RC but still loads 22 B4 very slowly and it is way too slow now. Blue circle spinning toooo much.  &lt;BR /&gt;
Lots of stuff to do in order to hunt down my problem.</description>
    <pubDate>Fri, 25 May 2018 01:07:43 GMT</pubDate>
    <dc:creator>Steve Jepson</dc:creator>
    <dc:date>2018-05-25T01:07:43Z</dc:date>
    <item>
      <title>Windows 10 April Update and DirectX/OpenGL issues</title>
      <link>https://community.graphisoft.com/t5/Installation-update/Windows-10-April-Update-and-DirectX-OpenGL-issues/m-p/292215#M30109</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Wondering if I am the only one who has noticed graphical glitching in AC21 after installing the latest Windows 10 'April' update?&lt;BR /&gt;
&lt;BR /&gt;
For me, in 3D openGL perspective view, when the file contains (or has ever contained) an object at a distant coordinate, I get severe jittering when navigating in the 3D window.  This is in files that do not exhibit the same behavior when opened on machines that have not yet been updated.  The behaviour is reminiscent of the rounding error symptoms described in this post &lt;A href="https://helpcenter.graphisoft.com/troubleshooting/3d-modeling/far-from-origin/" target="_blank"&gt;&lt;LINK_TEXT text="https://helpcenter.graphisoft.com/troub ... om-origin/"&gt;https://helpcenter.graphisoft.com/troubleshooting/3d-modeling/far-from-origin/&lt;/LINK_TEXT&gt;&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Sadly, even after eliminating all objects in the file, saving and rebooting, then placing a single wall or other object right at the project origin, the behaviour continues.  It appears like the 'centre of mass' coordinates for the project are not getting updated by ArchiCAD, or this information is not being communicated to the graphics driver under the latest windows update.  Basically files seem to become irreversibly 'tainted' by the memory of a distant coordinate - which could be a serious problem in any active project should anyone accidentally place something far away - eg by importing a surveyors dwg file.&lt;BR /&gt;
&lt;BR /&gt;
Axonometric views, and CPU calculated perspective modes are not affected by the jitter - only OpenGL perspective views.  (unfortunately, my most used 3D view).&lt;BR /&gt;
&lt;BR /&gt;
I have eliminated graphic drivers as the cause, by testing the default windows certified Nvidia driver, the latest updated driver direct from Nvidia, and the driver version that works without issues on other PC that has not received the 'April' update. &lt;BR /&gt;
&lt;BR /&gt;
Also, in pallets and object dialogs, there is no longer a flashing cursor visible when a text field is active - there is no feedback at all indicating that the field is active (or which field is active) until you type something.&lt;BR /&gt;
&lt;BR /&gt;
Only ArchiCAD seems to be impacted adversely by the April update - so far no other apps I use seem to have any problems.&lt;BR /&gt;
&lt;BR /&gt;
Have others experienced this?&lt;BR /&gt;
&lt;BR /&gt;
Has anyone resolved the issue?&lt;BR /&gt;
&lt;BR /&gt;
Unfortunately, it appears there is no way to roll back this update more than 10 days after it was installed - (without knowing in advance that you may want to - in which case there is apparently a CLI hack that can extend the roll back period)  After this period has expired, the only recourse is apparently to reinstall windows, losing all apps and settings, and to block windows updates thereafter.&lt;BR /&gt;
&lt;BR /&gt;
System afflicted has specs as per signature below&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 23 May 2018 12:10:47 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Installation-update/Windows-10-April-Update-and-DirectX-OpenGL-issues/m-p/292215#M30109</guid>
      <dc:creator>Paul King</dc:creator>
      <dc:date>2018-05-23T12:10:47Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 April Update and DirectX/OpenGL issues</title>
      <link>https://community.graphisoft.com/t5/Installation-update/Windows-10-April-Update-and-DirectX-OpenGL-issues/m-p/292216#M30110</link>
      <description>To answer my own issue, I now think I know the cause of the OpenGL  view jittering issue, and have a workaround&lt;BR /&gt;
&lt;BR /&gt;
I believe after testing that the distant origin issue does not require that any objects are (or have been) far from the project origin.  What is required is the CAMERA in use has been defined far from the project origin.  &lt;BR /&gt;
&lt;BR /&gt;
I suspect that there is a default camera position which is defined when the project is first generated (even though there is no explicit camera object), and that this does not move even when the viewpoint you see  while navigating in 3D openGL window moves.&lt;BR /&gt;
&lt;BR /&gt;
By explicitly &lt;B&gt;moving&lt;/B&gt; the camera position close to the object being viewed (rather than just flying or zooming/panning your viewpoint there), the problem goes away. (this can be done in 3D projection settings)&lt;BR /&gt;
&lt;BR /&gt;
The issue in my case arose I think when I imported survey data to create my site terrain, and the surveyors data appeared far from the project origin (and the default camera position).  &lt;BR /&gt;
Moving the project origin close to the imported objects, and clicking 'fit all' in 3D window (or otherwise flying the openGL viewpoint to the distant objects) meant the 3D view point calculated in openGL  *seemed* normal, but was getting rounding errors due to large offset distance from initial/default camera location still in use.&lt;BR /&gt;
&lt;BR /&gt;
The missing cursor issue in object dialogs and pallets remains for me at least, but at least one mystery solved.</description>
      <pubDate>Thu, 24 May 2018 11:39:37 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Installation-update/Windows-10-April-Update-and-DirectX-OpenGL-issues/m-p/292216#M30110</guid>
      <dc:creator>Paul King</dc:creator>
      <dc:date>2018-05-24T11:39:37Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 April Update and DirectX/OpenGL issues</title>
      <link>https://community.graphisoft.com/t5/Installation-update/Windows-10-April-Update-and-DirectX-OpenGL-issues/m-p/292217#M30111</link>
      <description>I have the same condition now.  Not sure where it is coming from.  I installed 22 RC and updated my Dongle, updated Windows, installed iCloud for Windows... all about the same time.  Checking for Updates with ArchiCAD said my dongle was out of date. Never seen that before.  Perhaps I should not have updated it.  &lt;BR /&gt;
&lt;BR /&gt;
Unitalled 22 RC but still loads 22 B4 very slowly and it is way too slow now. Blue circle spinning toooo much.  &lt;BR /&gt;
Lots of stuff to do in order to hunt down my problem.</description>
      <pubDate>Fri, 25 May 2018 01:07:43 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Installation-update/Windows-10-April-Update-and-DirectX-OpenGL-issues/m-p/292217#M30111</guid>
      <dc:creator>Steve Jepson</dc:creator>
      <dc:date>2018-05-25T01:07:43Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 April Update and DirectX/OpenGL issues</title>
      <link>https://community.graphisoft.com/t5/Installation-update/Windows-10-April-Update-and-DirectX-OpenGL-issues/m-p/292218#M30112</link>
      <description>I received the info from GRAPHISOFT that after a Windows update it is a good idea to update graphics drivers as well. See if that helps with the issue.</description>
      <pubDate>Mon, 28 May 2018 12:51:55 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Installation-update/Windows-10-April-Update-and-DirectX-OpenGL-issues/m-p/292218#M30112</guid>
      <dc:creator>Laszlo Nagy</dc:creator>
      <dc:date>2018-05-28T12:51:55Z</dc:date>
    </item>
  </channel>
</rss>

