<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Gilles Bertrand's Communities Activities</title><link>https://communities.bentley.com/members/ed268089_2d00_2d1d_2d00_4776_2d00_a6e1_2d00_6b0f36b28748</link><description>Recent activity for people in Gilles Bertrand's community</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>iTwin don&amp;#39;t find texture of OBM model when synchronisation</title><link>https://communities.bentley.com/products/digital-twin-cloud-services/itwin-services/f/itwin-services-forum/244564/itwin-don-t-find-texture-of-obm-model-when-synchronisation</link><pubDate>Tue, 25 Apr 2023 11:32:22 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f6e82a98-9f71-40b1-9e1b-13e188dbc746</guid><dc:creator>Gilles Bertrand</dc:creator><description>&lt;p&gt;When using iTwin and a model from OBM 10.12.1.83 and doing a connection with that DGN file containing the bridge model I get error messages concerning the texture not being found on PW. The file is on Projectwise and iTwin is working fine with ORD files, including SUDA components. The workspace and worksets are on PW and we have no issues when creating OBM model and referencing it in other DGN ORD files. See message below:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img style="max-height:240px;max-width:320px;" src="/resized-image/__size/640x480/__key/communityserver-discussions-components-files/343658/pastedimage1682422342902v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="/resized-image/__size/640x480/__key/communityserver-discussions-components-files/343658/itwin_5F00_issue01.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Category is Visual Fidelity&lt;/p&gt;
&lt;p&gt;Type Material.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Ask A Question II</title><link>https://communities.bentley.com/achievements/cd3cd235-25c1-476e-bb88-33a5705ca45a</link><pubDate>Fri, 01 May 2020 16:07:05 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:bb79ccb5-6a68-467a-b8f0-f9c594b4ea73</guid><dc:creator /><description>Ask 10 questions in a forum.</description></item><item><title>TERRAIN MODEL NOT VISIBLE WHEN PRINTING CROSS SECTION IN ORD</title><link>https://communities.bentley.com/products/microstation/microstation_printing/f/printing-and-plotting-forum/177186/terrain-model-not-visible-when-printing-cross-section-in-ord</link><pubDate>Tue, 26 Mar 2019 13:12:27 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:41246b42-b28c-43c2-b301-04da53dff998</guid><dc:creator>Gilles Bertrand</dc:creator><description>&lt;p&gt;Hi all,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;we just started a new project with OpenRoads Designer. I&amp;#39;ve setup the DGNLIB that needs to be configure the Named Boundary process for creating Plan, Profle and Cross section drawing. That is going well. I have my border, drawing model and sheet model created in my DGN file at the right scale and the annotations are fine. The only problem is when i try to print a PDF file, in sheet model, the existing ground (reference - named boundary - terrain model) is not visible in the PDF. But it is in the drawing model, sheet model. I can snap to it in the drawing model.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Any idea?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Gilles&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Ask A Question I</title><link>https://communities.bentley.com/achievements/460ac7df-7ccc-4c42-a204-9e05eef3be09</link><pubDate>Fri, 20 Jul 2018 00:51:04 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:a6d212d9-1496-48c5-9146-f903ba2b56a4</guid><dc:creator /><description>Ask a question in a forum.</description></item></channel></rss>