Cross Section Issues

I am attempting to create my XS sheets and having some issues. It started with the Create Cross Sections. I kept having to re-run my XS due to making changes to my model. So what I would do is delete the previous XS model, then run a new one. After several times needing to do this, when I would try to hit apply to create a new XS model, nothing would happen.

I then decided to create a new file and everything worked fine. Then the same sort of thing started happening with my Label Cross Sections. My Surface dropdown had nothing in it. Also, when I would go to Features - Annotate, my Cross Features window had nothing in it. 

I then asked someone else in the office to open the file and everything was working just fine for them in the same file. At the same time they were checking that, I again tried creating a new file and was able to run my new XS model and then label my XS as well.

It seems like something is happening on my machine where if I run the XS too many times, it breaks the file and I can no longer use it to run XS. I already tried deleting my resource files, but if anyone has a solution, please let me know.

Also, is there a better way to update by XS model besides just deleting it and creating a new one? I know I could probably just run in the sections that changed, but I figured it was easier to make a new model since I hadnt done any labeling or anything with the previous run.

Thanks

  • I have nothing in my sheet model. I havent even gotten to creating sheets yet. Just had it happen again. I have my Exist. model which has all my existing ground XS with R/W and all that stuff that wont change. I created a proposed model. Now I need to update a few XS, so I am trying to create an Update model, and then merge those into my proposed, but the Apply button does nothing again.

    Zachary Billings, P.E.

    Senior Roadway Engineer (Licensed in FL and MI)

    CONSOR Engineers, LLC

    System Info:

    Windows 11 | Intel Core i7-13700k | Nvidia RTX 4090 FE | 32 GB of RAM | 2 TB Western Digital Black SN850x NVME

    ORD Version 10.12.02.004 | FDOT Connect Version 10.12.01.00

    YouTube Page for ORD: https://tinyurl.com/BillingsCADD

  • make sure you turn on all levels on in the 3D model attached, then in the general tab you should see the surface populated
  • I cant even get as far as labeling currently. I just need to create a new run of XS to make some updates. Hitting the Apply does nothing. It seems like each file has a limited number of XS runs it will process before it just doesnt do it anymore.

    Zachary Billings, P.E.

    Senior Roadway Engineer (Licensed in FL and MI)

    CONSOR Engineers, LLC

    System Info:

    Windows 11 | Intel Core i7-13700k | Nvidia RTX 4090 FE | 32 GB of RAM | 2 TB Western Digital Black SN850x NVME

    ORD Version 10.12.02.004 | FDOT Connect Version 10.12.01.00

    YouTube Page for ORD: https://tinyurl.com/BillingsCADD

  • Mike, I had a question about cutting the sheets. When I cut the sheets, it is pulling in my Exist. model that has my existing ground, R/W, and other ancillary features. The issue is that the clips are not large enough to show all of the proposed stuff such as proposed ground, text, etc. I suppose the question is how do I make it so that the sheet cell program creates an appropriate clip to show everything in my XS?

    Zachary Billings, P.E.

    Senior Roadway Engineer (Licensed in FL and MI)

    CONSOR Engineers, LLC

    System Info:

    Windows 11 | Intel Core i7-13700k | Nvidia RTX 4090 FE | 32 GB of RAM | 2 TB Western Digital Black SN850x NVME

    ORD Version 10.12.02.004 | FDOT Connect Version 10.12.01.00

    YouTube Page for ORD: https://tinyurl.com/BillingsCADD

  • This looks very familiar. It may have nothing to do with PowerGeoPak. Try accessing the User Preferences in GeoPAK (GeoPak - Road - User Preferences) and then select the magnifying glass next to "working directory". If you don't see a drive letter (i.e. c:\ or network drive letters, just a profile name and the word Desktop) then the solution should be straight forward.

    Check the number of Desktop shortcuts you have, if the number is lets say 100 or 200, try moving these desktop shortcuts to say "C:\Temp" for example and see how PowerGeoPAK responds afterwards. You may need to close out of FDOTSS4 (or your version of the FDOT client) and then go back in. If your issue is related to reaching the max number of supported Windows Desktop shortcuts then the issue should hopefully be resolved for you. Note: The Desktop shortcut issue could potentially affect other applications as well.