Can you get round to fixing this bug which has plagued it since year dot.

e.g.:

*the constant re-introduction of deleted restraint numbers.

Thanks

:thumbup:

oh, and the constant revert to case #1 on the API610 processor

Cheers.

Can you please provide more details?

Richard,

While I cannot explain the issue with the API610 processor, the reappearing restraint has been an issue for a while. This problem becomes prevalant when trying to troubleshoot overstressed pipe.

When eliminating restraints from an element, we have 2 options: 1) double click the Restraints check box, or 2) manually delete text from the text boxes in the Restraints tab.

The problem occurs when the user attempts to perform operation number 2. While editting the element, all appears as it should be. However, selecting another element and returning to the original element (sometimes) results in parts of the text that was there previously to come back. Sometimes it returns if you focus the attention to another text box; sometimes it only returns when you go to a different element and come back.

Since selecting another element and coming back is an added step that's easy to miss, this mis-entered restraint typically makes it over into the model-checking phase.

Whether the information is actually omitted or not is oftentimes spotty. The rate of encountering the problem makes it unclear what I as the user am doing to cause it (if it is a user workflow issue). Complex restraint setups typically mean it's just a glitch with CAESAR II that I have to live with, rather than try to manually input it myself.

Michael,

Thank you for this explanation. This is something we can work with.

Using CII for a large model at the moment.

More Common Faults:

*Not picking up ALL of the nodes when rotating model using Graphic select. Drives me ******* nuts to have to search 800+ nodes for an un-rotated element.
*Branch error check showing a fail which disappears if you shut-down and then re-open file
*Graphics (hoops) program stuck in the 1990's. very poor rendition of models, especially during zoom/pan
*As always, constant,constant crashes. no matter how small or big model is.

*Just recieved this from H/O:



What the above highlights to me as an end user, is just how finicky and unstable a platform the CII program is.

On a personal note, I've FEEL that i have seen very little real development of the CII program, apart from an odd tweak here- or there in the last few years.
Its difficult to to come to the conclusion that the CII program has become a cash cow, especially as the price of it is going through the roof.

Now that we have Intergraph on board and a 40%+ price increase, are we going to see a real development of the platform? i hope so.

And for the record, i've always worn my heart on my sleeve and i believe you guys welcome open critizem, if through discussion. you show that my above opinion is grossly wrong, i'll gladly apolagise.

Best regards,

TJN

I agree with the sentiments of TJN.
My own personal gripe is with the graphics. Opening a large model should not be an issue with modern computing.

Ok,
So far, with the instalation of 5.3 i have booked 25 hrs to overheads as CII is getting more buggy by the day.

WRC107 is to be patched. (Awaiting)

Now, my animation processor is borked.
Plus, my file crashed.

Honestly. everytime i upgrade CII i regret it. its an awful program and well in need of a complete re-write.

Now, to compound that, my service centre has been zapped by integraph and i have no where to go for services ( that i am aware of yet anyway)

I appreciate this sounds like im a wingebag, but really, its extremely fustrating.

Trust me, we're frustrated too. Version 5.30 was more heavily tested than any previous version. We had the largest group of "beta testers" ever. Still, no one found the issues with the WRC module (which was a rewrite of the interface, as you suggested).


Regarding the animation module, have your tried switching the video driver from OPENGL to "Windows Basic"? Can you describe the problem? (Version 5.30 was used here in our November seminar, just before the DVD master was generated. There were no issues encountered with the animation module - or any other module in the package.)

What crashed, where? Was there an error diagnostic message?

I've tried to send you an update (hot-fix) for the WRC problem, but it bounced back due to your "corporate security". Can you send an alternate e-mail address to TechSupport?