Unable to re-open file in OpenVSP 3.11

[corp...@gmail.com]

Hi,

great job with new blending function in release 3.11 !!

 But unfortunately I have faced the same problem I had with a previous release : after some manipulating using new release  and closing the file  I can't re-open it anymore and OpenVSP crashes every time i try to open it .

I'm working in Windows10 and 64 bit system. Could it matter in some way ?.

Regards
Corrado

[Rob McDonald]

I don't understand why you're seeing this behavior -- I don't know
that anyone else has had the same issue.

Can you send me this example of a file that crashes when you open it?

Rob

> --
> You received this message because you are subscribed to the Google Groups
> "OpenVSP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to openvsp+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Gigi]

It is happening to me also. With previous release also.

It opens file buth what was nice looking project that I spent hours on, now is useles BS. File is attached.

[Gigi]

Forgot:  this is in W10 64bit.

In W7 (in Virtual box) VSP crashing

In Win XP 32 bit (virtual box) VSP crashing

[corp...@gmail.com]

Hi Gigi,

I managed the problem thanks to Rob's help, but I' m still testing the release Rob sent me in that it seemd a  problem related to different standards between Europe and USA concernig commas and point . I had ,first, the same result you show in your first picture above ( all model distorted) then I found impossibile to run VSP Aero in VLM mode since the solver monitor everytime showed errors in the paneling procedure.

The first problem  seems , at the moment, solved but I'm working progressively on the same model, introducing new features, saving, closing and openig again, in order to check further problems. By now ti works.

This second problem was due to tip treatment panel: I was using the round tip cap type, but in version 3.11 for some reason,it didn't work for me. Testing further I found that only "none" make possible to run correctly VSP Aero. Since it is a minor problem I'm currently going on without any tip cap treatment.

Corrado

[Rob McDonald]

Gigi,

I'm sorry you're facing this frustration.

As Corrado mentions, we've noticed that this is associated with the *.vsp3 file using commas instead of periods as the decimal indicator.  Unfortunately, I don't have any idea how this happens.

Did you ever open the *.vsp3 file in any other editor?

Were there any strange/odd/unusual steps taken through the creation of this model?

Although Corrado experienced this problem, he has been unable to duplicate it since then.  Until we can figure out a way to duplicate the problem, we're helpless to fix it.

Rob

--
You received this message because you are subscribed to the Google Groups "OpenVSP" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openvsp+unsubscribe@googlegroups.com.

[Gigi]

Hi Rob.

Last night I was working on this hydrofoil for a sailboat. I was aware of possible problem so I exported file in the format that I needed. So last night I closed VSP, and reopen again this file, and there was this problem. I tried one more time and everything was fine ?????

Unfortunately this morning I was unable to continue to work on file.

Not opened in any other editor.

Here are my regional settings: , for decimal?

do you sugest I change regional settings so . is decimal?

To unsubscribe from this group and stop receiving emails from it, send an email to openvsp+u...@googlegroups.com.

[Rob McDonald]

These sorts of settings on your computer are called the 'locale'.  The 'C' locale is the default and uses periods as the decimal separator.  OpenVSP should ignore your computer's settings and instead use the 'C' locale for everything.

It appears that somehow OpenVSP's desired default C locale is getting overridden by some combination of operations.

I prepared a special OpenVSP that prints out locale-related diagnostic messages at startup, shutdown, file open and save...  You can get it here...

http://www.openvsp.org/zips/OpenVSP-3.11.0-win32_locale.zip

If you can recreate a process that leads to a file saved with comma-delimiters, please do that and send me the output to the black console for that run.

BTW, which format did you export?  There is a possibility that the export code is what is changing the locale setting...  Any step may be a clue.

Rob

To unsubscribe from this group and stop receiving emails from it, send an email to openvsp+unsubscribe@googlegroups.com.

[Gigi]

I exported to step and igs.

I have plenty files that I cant open, but not important ones so far. 

I open some files in notepad and indeed coma is in files that I cant open. Ones that I can open have period as decimal separator.

I opened my file in notepad and replaced , with .  

Now file opens but VSP crashes as soon as I click Geom Browser.

Here is printout from console:

Startup locale is: C

error : No such file or directory

and

Startup locale is: C

Write vsp3 locale is: C

Write vsp3 complete locale is: C

[Rob McDonald]

A global search & replace probably won't work -- there are some things (for example, lists of numbers) where we expect commas to appear.

If you could go through a cycle like this -- and report the console output for each step...

OpenVSP

Add some components

Save *.vsp3 file

Export IGES

Save *.vsp3 file (different name)

Export STEP

Save *.vsp3 file (different name again)

Exit OpenVSP

Then, report the console -- and which files have comma decimal separators.

This will hopefully tell us exactly which operation is changing the locale on us.

Thanks,

Rob

To unsubscribe from this group and stop receiving emails from it, send an email to openvsp+unsubscribe@googlegroups.com.

[Gigi]

I figured out how to fix file by manually editing it in notepad.

When I manage to reproduce proble I'll post here.

Thanks,

Gigi

PS. While I have your attention  Rob, is there way to export quadrilateral mesh? For use with APAME SOLVER 

[Rob McDonald]

Glad you were able to get your file repaired.  For simple-ish files, it shouldn't be too bad.

APAME isn't just quadrilateral -- it needs a structured mesh.

If you are modeling a wing-alone, you can probably hack something together to put a XSec (*.hrm) file from OpenVSP into APAME's format.

Unfortunately, when you have multiple components intersecting, this won't work.

You should also check out VSPAERO's Panel method capability.

Rob

To unsubscribe from this group and stop receiving emails from it, send an email to openvsp+unsubscribe@googlegroups.com.

[Gigi]

Thanks, I will look into XSec file.

Console does not write nothing on iges export? console:(error : No such file or directory)

Please help with one more thing: I am struggling to align (shift x coord) all section so that all trailing edges lie on a plane (y-z plane), is there simple way to do this? Basically I would need to change airfoils section datum from leading edge to trailing edge.

[Rob McDonald]

On Monday, March 27, 2017 at 7:52:04 PM UTC-7, Gigi wrote:

Thanks, I will look into XSec file.

Console does not write nothing on iges export? console:(error : No such file or directory)

There should be no console output for IGES (and most operations).

After you export an IGES file, then go save a *.vsp3 file -- to see if it then changes to commas. 

Please help with one more thing: I am struggling to align (shift x coord) all section so that all trailing edges lie on a plane (y-z plane), is there simple way to do this? Basically I would need to change airfoils section datum from leading edge to trailing edge.

You can change the sweep reference line to the trailing edge.  Then set the sweep angle to zero.

This takes a little trick -- there is also a way to set a secondary sweep angle -- and the reference location for that sweep.  The two reference locations can not be equal.  The secondary one defaults to the trailing edge (1.0).

So, to change the primary sweep reference to 1.0, first change Sec SW Loc to 0.5 (for example) and then change Sweep Loc to 1.0 -- then change the sweep angle to 0.0.

Rob

[Gigi]

Thanks for help. 

I cant recreate poblem so far.

Write vsp3 complete locale is: C

Write vsp3 locale is: C

Write vsp3 complete locale is: C

Write vsp3 locale is: C

Write vsp3 complete locale is: C

EJINFIIAHQ

EJINFIIAHQ

EJINFIIAHQ

Write vsp3 locale is: C

Write vsp3 complete locale is: C

EJINFIIAHQ

EJINFIIAHQ

EJINFIIAHQ

EJINFIIAHQ

EJINFIIAHQ

EJINFIIAHQ

EJINFIIAHQ

EJINFIIAHQ

EJINFIIAHQ

EJINFIIAHQ

Write vsp3 locale is: C

Write vsp3 complete locale is: C

Write vsp3 locale is: C

Write vsp3 complete locale is: C

[Rob McDonald]

Interesting. Thanks for trying. This one looks like it is going to
be tough to track down...

Did you do anything else during the session that lead to problems?
Perhaps you let your computer go to sleep and restore? Did you write
out any other file types? Did you use any other OpenVSP features?

Do you know what you're doing that causes OpenVSP to write out
EJINFIIAHQ? It looks like a 10-digit Geom ID, but 'normal' OpenVSP
code doesn't print those out -- and my diagnostic version didn't add
anything to print them out.

Are you using a custom component that may print out a GeomID? Are you
running a script that may print one out?

Rob

[Gigi]

Here is some more from console:

Startup locale is: C

Write vsp3 locale is: C

Write vsp3 complete locale is: C

Write vsp3 locale is: C

Write vsp3 complete locale is: C

Write vsp3 locale is: C

Write vsp3 complete locale is: C

Write vsp3 locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 complete locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 complete locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 complete locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 complete locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 complete locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 complete locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 complete locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 complete locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 complete locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

Write vsp3 complete locale is: LC_COLLATE=C;LC_CTYPE=C;LC_MONETARY=C;LC_NUMERIC=English_United States.1252;LC_TIME=C

I am still not recreating problems. I have opened file and there are commas...

Dana utorak, 28. ožujka 2017. u 19:02:26 UTC+4, korisnik Rob McDonald napisao je:

Interesting.  Thanks for trying.  This one looks like it is going to
be tough to track down...

Did you do anything else during the session that lead to problems? Plenty
Perhaps you let your computer go to sleep and restore? NO/Maybe Did you write
out any other file types? Again STP and IGS. With various settings (convert tu cubic, split surfaces, etc) Did you use any other OpenVSP features? Just modeling

Do you know what you're doing that causes OpenVSP to write out

EJINFIIAHQ? Have no idea. it just started to write like that It looks like a 10-digit Geom ID, but 'normal' OpenVSP

code doesn't print those out -- and my diagnostic version didn't add
anything to print them out.

Are you using a custom component that may print out a GeomID?  NO Are you
running a script that may print one out? No

It looks like there is only few of us with problem. Is it possible to code some tool to repair files? Manually is possible but tedious...

[Rob McDonald]

Ok, this is progress!

What did you do before the locale string changed from just 'C' to the
longer message?

The longer one is 'C' for most things, but
LC_NUMERIC=English_United_States -- which should still be decimals.
However, it may be that your computer has changed that setting to be
commas.

OpenVSP shouldn't ever have a different locale. Yours changes between
your third and fourth save operation...

> It looks like there is only few of us with problem. Is it possible to code
> some tool to repair files? Manually is possible but tedious...

Unfortunately, I don't think that will be easy.

My hope is to fix the problem and make it go away for good.

Rob

[Gigi]

Dana utorak, 28. ožujka 2017. u 22:59:38 UTC+4, korisnik Rob McDonald napisao je:

Ok, this is progress!

What did you do before the locale string changed from just 'C' to the

longer message?  Same: editing geometry. Cant think of any special action. I run VSP from two different partitions. Dont think this is cause. I had problem since 2.9 majbe... Tried puting PC to sleep, nothing. Tried various geom display options...no luck. I will keep an eye on console...

[Gigi]

Hi Rob,

Just to let you know, this problem wit full stop and comma scrambling is still here and gives me lot of problems...


thanks

Vjeko

[Rob McDonald]

OK,

I haven't been able to debug it, but I think it may be related to writing either STEP or IGES files -- do you do that regularly?

Please create a simple file with just a Pod.

Then, open that file -- then save-as a different name.  

Then do the same, but open, export STEP or IGES, then save-as a different name.

If you can then verify that the file that comes after writing a STEP/IGES file uses commas as a decimal marker, that would be great.

If this is true -- the easy fix is to save before exporting these files -- then terminate OpenVSP and restart before continuing work.

Do you have the ability to compile your own OpenVSP?  If I prepare a debug branch on GitHub, can you build it?

Rob

[Gigi]

I think you are spot on. Iges export out was last time I think.
I have no clue about compiling. What do I need to do that?

[Rob McDonald]

Don't worry about compiling.

Can you run the above test to generate the files described above?  That should confirm that the problem resides with the IGES export.

Thanks,

Rob

On Mon, Jan 21, 2019 at 4:21 AM Gigi <fibra...@gmail.com> wrote:

I think you are spot on. Iges export out was last time I think.
I have no clue about compiling. What do I need to do that?

[Gigi]

Yes, I confirm it is iges export. If you don't save after export there is no problem, but if you save then file gets mesed up.

Did not tried step export.

still no way to fix files? other than manual?

Thanks 

Vjeko

[Rob McDonald]

Thanks for chasing that down.  I will try to integrate a permanent fix when I get a chance.

I don't have an immediate answer for restoring a damaged file.  I would try starting with an XML editor -- something that knows the difference between the tags and the data in the tags.  (A plain text editor will treat them all the same).  Then, I would try to search & replace the fields.

The thing to watch out for is places where we really use commas to separate numbers -- things like airfoil points read in from a file, etc.

Rob

[Gigi]

Glad to contribute.
Any chance that some geometry import (Iges or step) will be implemented anytime soon? Thing is, Vsp files that I lost due to export are actually ones that something was made from them, or were used for cfd studies. If I could import geometry back it would be easy to recreate Vsp geometry... I believe this is feature request 😄

[Rob McDonald]

I have an idea to make a version of OpenVSP that might be able to 'rescue' your files -- it probably won't work, and I'm not going to have time to do it for a while, but I'll give it a try when I can.

We won't ever be able to import STEP or IGES files.  However, if you can open your IGES files in a CAD program and create a STL mesh, you can import that into OpenVSP.  It won't be a parametric model, but it is a starting point for recreating your work.

Rob

On Mon, Jan 21, 2019 at 11:10 PM Gigi <fibra...@gmail.com> wrote:

Glad to contribute.
Any chance that some geometry import (Iges or step) will be implemented anytime soon? Thing is, Vsp files that I lost due to export are actually ones that something was made from them, or were used for cfd studies. If I could import geometry back it would be easy to recreate Vsp geometry... I believe this is feature request 😄

[Gigi]

Great! 

As for stl, great again. iges or step or stl, doesn't mater. As long as it is dead geometry.

Thanx

[Rob McDonald]

Gigi --

Please do me a favor -- try this out...

OpenVSP

Add a Pod

Export an IGES file -- junk.iges

Click File -- New -- to clear the model

Open one of your corrupted files.

It probably won't work -- but if it successfully opens, then I think I will be able to figure out a way to salvage your damaged files.

Let me know,

Rob