Problem Accepting mesh on zaxxon method

Onkel_Micha · Feb 12, 2012

Hello,

I am working still on my hill climb track (but I need to proceed also with job and university, so I have very less time for it). I found Zaxxon's method (great work Zaxxon, really great) and let the scripts run. But:

After creating the mesh I tried to accept it and it crash. It runs until it reach 0.999 and then, BANG!, failed. I let all scripts runs a second time and again. Failed.

If I use "simplificar" first times with 4-times okay and then it creates three files. But the ply-files are 0KB big.

I don't have any idea where I made something wrong. Further I can't find the video tuts because megaupload sites don't open.
Help please. I didn't understand the terrain topics at all. Even if I read all docs I didn't find the mistake. ;-(

Thanks and best regards

Michael

lakimakromedia · Feb 12, 2012

Without Zaxxon help, finish any project with this method is impossiblem. Only few people on whole world can build in this method, but they are only 0.00000000000001% of all trackmakers.

Regards
L.

PS
I know only 3 persons how can build something in this method without problems, and one of them is Zaxxon LOL

liquido · Feb 13, 2012

You have to show a capture showing the Octave info about the crash, without that nobody can help you.

You can find Zaxxon at SimRacing.es, and also you can find here new links for video turorials.

http://foro.simracing.es/bobs-track-builder/3815-tutorial-ma-zaxxon.html

Palesportes can help you if you can´t find zaxxon at this link:

http://www.plpcreation.tonsite.biz/

Onkel_Micha · Feb 13, 2012

Okay, I will Let it Run tomorrow during The day then I could send The Crash screenshot.

Ehrlec gave me maybe the right hint. I tought surface 222 will be created by gmsh. Hope I will understand how it works.

Thanks for The links.

My Spanish is more than Poor. (The typo mistakes here come from iPad auto-correct!)

liquido · Feb 14, 2012

My onw Gmsh videotutorial (in spanish, sorry)

http://www.mediafire.com/file/fcgfy67999cdal3/Tuto Gmsh.mp4

You define the Physical surface (111) and (222) in Gsmh, but you have to call them as Physical Surface with another software to open the anchors_carretera.geo and write inside it as a word processor, to write a comand inside( I use notepad++ it comes with Octave)

1. Physical surface (111)
Zaxxon's scripts have generated a file inside S1_mesh/salida folder called phys111.txt copy the entire contents of the file and paste inside your Anchors_carretera.geo at the end of the file, following that example:

Physical Surface (111) = {phys111.txt content};

2. Physical surface (222)
Inside geometry menu go to elemental entities/add/new/1º ponits 2º spline 3º plane surface.

First you have to set points to define a spline using that points (that spline will be the outer boundary of your undriveable terrain, and finally define the physical surface (222)
The 222 surface is defined by the spline that you have generated by connecting the points that we have also set ourselves and the splines that define the outer boundary of the area TransTable (physical surface 111) go to notepad++ and open anchors_carretera.geo look for the last plane surface generated in the file... this is the physical surface (222) so take the numeric name of that plane surface and use it to define your physical surface (222) like in the following example.

Physical Surface (222) = {your last plane surface};

The Best part of Zaxxon Method is that becomes really easy to work with it... I kwon more than 3 persons that use the method without problems.... for sure thanks to zaxxon explanations and tutorials... but it is not a hard way... it is a new way.

Onkel_Micha · Feb 14, 2012

Hi ,

many thanks for the help. I will watch the video within the next minutes.

Okay, what I understood:

I open phys111.txt => copy this content into anchors_carretera.geo with the line

Physical Surface (111) = {Nsup00568+1,Nsup00568+2,Nsup00568+3,Nsup00568+4,Nsup00568+5,Nsup00568+6,Nsup00568+7,Nsup00568+8,Nsup00568+9,Nsup00568+10,Nsup00568+11,Nsup00568+12,Nsup00568+13,Nsup00568+14,Nsup00568+15,Nsup00568+16,Nsup00568+17,Nsup00568+18,Nsup00568+19,Nsup00568+20,Nsup00568+21,Nsup00568+22,Nsup00568+23,Nsup00568+24,Nsup00568+25,Nsup00568+26,Nsup00568+27,Nsup00568+28,Nsup00568+29,Nsup00568+30,Nsup00568+31,Nsup00568+32,Nsup00568+33,Nsup00568+34,Nsup00568+35,Nsup00568+36,Nsup00568+37,Nsup00568+38,Nsup00568+39,Nsup00568+40,Nsup00568+41,Nsup00568+42,Nsup00568+43,Nsup00568+44,Nsup00568+45,Nsup00568+46,Nsup00568+47,Nsup00568+48,Nsup00568+49,Nsup00568+50,Nsup00568+51,Nsup00568+52,Nsup00568+53,Nsup00568+54,Nsup00568+55,Nsup00568+56,Nsup00568+57,Nsup00568+58,Nsup00568+59,Nsup00568+60,Nsup00568+61,Nsup00568+62,Nsup00568+63,Nsup00568+64,Nsup00568+65,Nsup00568+66,Nsup00568+67,Nsup00568+68,Nsup00568+69,Nsup00568+70,Nsup00568+71,Nsup00568+72,Nsup00568+73,Nsup00568+74,Nsup00568+75,Nsup00568+76,Nsup00568+77,Nsup00568+78,Nsup00568+79,Nsup00568+80,Nsup00568+81,Nsup00568+82,Nsup00568+83,Nsup00568+84,Nsup00568+85,Nsup00568+86,Nsup00568+87,Nsup00568+88,Nsup00568+89,Nsup00568+90};

Physical Surface (222) = {Plane Surface (Nsup00568+89)={l2}};

Is it right?

I would say it is not a hard way, but it takes time to understand it. Especially if I try to create a track next to a busy life. But the scripts run fantastic on a hidden computer in my office.

Thank you all for your support. I really appreciate this.

Bye

Michael

liquido · Feb 15, 2012

No at all

Physical Surface (111) = {Nsup00568+1,Nsup00568+2,Nsup00568+3,Nsup00568+4,Nsup00568+5,Nsup00568+6,Nsup00568+7,Nsup00568+8,Nsup00568+9,Nsup00568+10,Nsup00568+11,Nsup00568+12,Nsup00568+13,Nsup00568+14,Nsup00568+15,Nsup00568+16,Nsup00568+17,Nsup00568+18,Nsup00568+19,Nsup00568+20,Nsup00568+21,Nsup00568+22,Nsup00568+23,Nsup00568+24,Nsup00568+25,Nsup00568+26,Nsup00568+27,Nsup00568+28,Nsup00568+29,Nsup00568+30,Nsup00568+31,Nsup00568+32,Nsup00568+33,Nsup00568+34,Nsup00568+35,Nsup00568+36,Nsup00568+37,Nsup00568+38,Nsup00568+39,Nsup00568+40,Nsup00568+41,Nsup00568+42,Nsup00568+43,Nsup00568+44,Nsup00568+45,Nsup00568+46,Nsup00568+47,Nsup00568+48,Nsup00568+49,Nsup00568+50,Nsup00568+51,Nsup00568+52,Nsup00568+53,Nsup00568+54,Nsup00568+55,Nsup00568+56,Nsup00568+57,Nsup00568+58,Nsup00568+59,Nsup00568+60,Nsup00568+61,Nsup00568+62,Nsup00568+63,Nsup00568+64,Nsup00568+65,Nsup00568+66,Nsup00568+67,Nsup00568+68,Nsup00568+69,Nsup00568+70,Nsup00568+71,Nsup00568+72,Nsup00568+73,Nsup00568+74,Nsup00568+75,Nsup00568+76,Nsup00568+77,Nsup00568+78,Nsup00568+79,Nsup00568+80,Nsup00568+81,Nsup00568+82,Nsup00568+83,Nsup00568+84,Nsup00568+85,Nsup00568+86,Nsup00568+87,Nsup00568+88,Nsup00568+89,Nsup00568+90};

That is perfect, because physical surface (111) is allready generated by zaxxon`s scripts but you have to open Gmsh and define the plane surface that will be called physical surface (222)

you have to do what I do in the Gmhs tutorial, place the nodes Inside geometry menu, go to elementary entities/add/new/1º points, then you have a new window .... every time you press the "e" you place a node inside Gmhs, when you have enough nodes to trace a spline with them, press "spline" in the Gmsh window... to trace the spline remark every node with the left mouse button to make a closed line.
at this point you should have something like this in gmsh

Then you have to define the plane surface, look one again in the gmsh window and press (plane surface) that will be formed by outer and inter boundary... the outer is the spline that you have done, the inter is the outer of physical surface (111)

Once you remark every spline with the left button of your mouse to define the outer and inter boundary of that surface, press the "e" to finish... then go to Notepad and take the last surface.... it will have a numeric name... like 5609... pyshical surface 222 used to be like that:

Physical Surface (222) = {4596};

liquido · Feb 15, 2012

Sorry for the off topic.

ehrlec I need your help at http://btbtracks-rbr.foroactivo.com/

Onkel_Micha · Feb 15, 2012

So, I didn't found the time to watch the video. But I have run mallado_regular(12,3) again and I will try to proceed tomorrow over the day to create the mesh and the surfaces. (Or should I load it up with phy111.txt inside, Ehrlec? )

zaxxon · Feb 17, 2012

ehrlec said:
Hola liquido, (liked your video) I've examined Michael's file.

Before continuing further, I would run again mallado_regular(12,3). Due to initial parameters used and the nature of switchbacks, the script failed to create organized paired triangles in many sections. The script is designed to form quads best it can for mapping but sometimes things just don’t work out as expected. Deleting the Transfinite surfaces to recreate them is causing Gmsh to crash in an unusual way for me. I think running mallado_regular again and shortening the distance via the 1st parameter might help. I rarely extend the drivable terrain beyond 15 meters from the road so I don't see these problems.

Disaster areas caused by the process when forming pairs in some situations:

Another issue not related to the script error is that the drivable and non-drivable elements were not connected. There is an overlap of elements (terrain faces on the road). Be careful when selecting (highlighting in red) the boundary splines and line segments. Only select the boundary lines and know where the boundaries are.

Here is an example of how Physical Surface(222) should be expressed:
Physical Surface(222)={40937};
In this case 40937 is the only Plane Surface number for the entire non-drivable terrain.

The initial script error was caused by improperly entering the Physical Surfaces.

"Force regular" option should not be marked unless you are sure you want a mesh like the one above. It is not checked by default and it should remain unchecked.

zaxxon · Feb 17, 2012

May be that option shouldn't be included in the GUI...
I use the GUI

As multiupload is down I will update the links to parlesporte's videotutorials as soon as I can.

Onkel_Micha · Feb 18, 2012

It was the regular parameters which are preselected. And yes, I checked "Force regular" I have done it to test if then then proceed on accepting the mesh. I always use the GUI (both). I am proceeding sometimes on the windows instance on my MacBook where it is more difficult to find the right buttons inside Octave. ;-)

I am just watching the tut from Liquido. I will push up the result later today when I hopefully made a success.

Update follows later today.

zaxxon · Feb 18, 2012

Ok, Onkel_Micha. It is really important that you check your mesh as liquido does. Using gmsh' visibility option check your Physical Surfaces. If your mesh is not ok, do NOT go on working with the scripts, but ask for help.

NOTE: I am still uploading parlesportes' videotutorials... I will update the links as soon as I am finished.

zaxxon · Feb 18, 2012

Onkel_Micha said:
I can't find the video tuts because megaupload sites don't open.

http://www.mediafire.com/?tspub5ub5ncqe

Onkel_Micha · Feb 18, 2012

Actual status:

Watched the video from Liquido (5 times to understand it), Main problem were two crossed lines which always caused problems. I simply changes the coordinates => works (I spend the hole day on this)

I have uploaded the geo and msh file

@ Liquido: If you want to see just let me know I will give you the login data for the folder.

Now I would try to accept the mesh. I didn't have any mesh as shown above. But I am not sure with Phys111 and 222.

@Zaxxon: Thanks for the upload. I will watch them tomorrow.

Thanks for all your help

Onkel_Micha · Feb 19, 2012

It doesn't work. Accepting the mesh still crash.

If I understand correct it should be the result of a wrong phys number. I tried to understand from Liquido tut what number I Need to take.

Where is The Point I am too stupid to understand?

zaxxon · Feb 19, 2012

I need to see your .geo. Give me a link to download it.
All the driveable surfaces must be in the Physical Surface 111 list.
All the non-driveable surfaces must be in the Physical Surface 222 list.

The most frequent situation is that you have only 1 plane surface for the non-driveable terrain and it is the last one you have created using gmsh. So you look for the last "Plane Surface" text in your .geo and copy its code in the 222 list. For one-track projects the file salida\phys111.txt has the list of driveable surfaces.