I installed the latest updates last week and have been having quite a few issues with slow performance.
The following hang-ups are occurring:
I have tried compressing files to no avail. I work on local files, typically on my OneDrive files that are on my E Drive. I tried copying to my C drive and there was no improvement. Both of these drives are NVME drives. All of these issues are also occurring on my virtual machine, so it’s not just my home computer.
Then I decided to try to open my files without the workspace. I just right clicked one of my files and hit open. NONE of the issues above were occurring. However, the following was still an issue:
I have posted a video to my YouTube page highlighting these issues: https://youtu.be/c_p2HTRADBU
Has anyone encountered these issues?
I would like to jump on this thread (because this is also related to 10.10.01.00) and also express that the warning dialog about the missing Geotechnical file is very obtrusive for those firms that utilize ProjectWise. Could this check be moved elsewhere in the file opening process rather than the compiled DLL, so that as consultants we could opt to remove it?
Eddie Giese, PEProduction Manager | Senior Roadway Engineer | AssociateLicensed in FL & PAACEC FDOTConnect Instructor on behalf of FDOT
Patel, Greene & Associates, LLC PowerGEOPAK V8i SS10 (08.11.09.918)OpenRoads Designer 2022 R3 (10.12.2.4)ProjectWise Explorer CE 10.0.3.453OpenRoads Conceptstation CONNECT Edition (10.0.16.84)LumenRT Pro CONNECT Edition (16.17.60.73)
Eddie, this is one of about 30 template files that are copied to a workset when a file is opened. It's complaining because the Geotechnical folder is missing in older worksets, and is part of the On File Open process. Bentley has not yet come up with a method to include this file when opening in ProjectWise and when it comes to quantities you will need the templates or build your quantities by hand.
Hey Bob,
Would it be possible to implement a Configuration Variable approach to the FDOT.OnFileOpen.dll File, allowing ProjectWise Users (in particular) to disable certain functions of the application? Perhaps something like (one idea):
ADDGEOTECHTEMPLATES=0 (disables the function to check for and copy Geotechnical Template Files to the Geotechnical Folder)
ADDCIVILTEMPLATELIBRARYFILE=0 (disables the function to check for and copy Template Library File to the applicable Folder)
Unfortunately, these Folders (that the FDOT programs are looking for) don't exist in the "backend" of ProjectWise Explorer. We would, of course, add these to the ProjectWise Folders (seen in ProjectWise Explorer).
ProjectWise Explorer CONNECT Edition, Version 10.00.03.453
ProjectWise Drive, Version 2022.1.328
OpenRoads Designer CONNECT Edition, Version 10.09.00.91
OpenRoads Designer CE 202 Release 2, Version 10.10.21.4
Power GEOPAK V8i (SELECTseries 10), Version 08.11.09.918
Eddie and Matt
Line 406 in the FDOT.cfg file in FDOTConnect10.10\Organization-Civil\ folder has a variable MS_DGNAPPS < FDOT.OnFileOpen if you place a # in the beginning it the dll will not run. i'm not a fan of this because of the othere functions this app performs but you will no longer see the warning message.
Let me ask a question, is there a Process running in the Task Manager on the local workstation when ProjectWise is in use?
Thanks Bob. Yeah, we will not be commenting out this variable definition as it will be essential for non-ProjectWise WorkSet activity. We are just hoping that a future release of the FDOT Connect 10.10 software will allow for some granular settings that can allow us to disable the functions that don't apply to the ProjectWise environment (only when we are working in ProjectWise). And then we are not working in ProjectWise, the WorkSpace would function as designed/delivered. It seems that using new Configuration Variables could facilitate this, without the need to revise FDOT delivered Configuration Files or other resources.
Hello Bob,
Yes sir, there is. It's Process Name is pwc.exe. The Process Description is ProjectWise Explorer.
i might be able to do something with that over the next few days if it's not too busy around here. want to volunteer as my tester?
Absolutely! Thank you so much for looking into this for us.
A better way might be to fetch a Configuration Variable for PW, is there a Main PW Variable. Like _ENGINENAME
This is where things can get a bit tricky. You can open Files in ProjectWise using a few methods:
Based on different methods and configuration scenarios, this variable could work (the Bentley programs seem to know when to define this variable without intervention):
_MCM_PWDISABLEINTEGRATION = 1 (Not working in ProjectWise; this is defined at the system level)
_MCM_PWDISABLEINTEGRATION = undefined (Working in ProjectWise)
If I open a File in ProjectWise (using any of the methods described above), the _MCM_PWDISABLEINTEGRATION variable is undefined. However, if I open a File outside of ProjectWise, the _MCM_PWDISABLEINTEGRATION variable is defined with a value of 1.