OSM first try
-
- Posts: 1420
- Joined: Tue Aug 25, 2020 7:07 am
OSM first try
Decided to give the OSM-Exporter a try today.
Looks very nice, thanks to the devs and especially to Wiek. Here the result at my home airport after 2 hours reading and doing
Looks very nice, thanks to the devs and especially to Wiek. Here the result at my home airport after 2 hours reading and doing
Visit https://www.baleit.no
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
-
- Posts: 1420
- Joined: Tue Aug 25, 2020 7:07 am
Re: OSM first try
My landscape is finished as far as I come for now. I thought first, it will be nice to add buildings automatically to the landscapes, but I was wrong: It is amazing!
The tool
The description is good, I followed it word by word and got it to run with the first try, I don't see a point in it worth to make it better.
The import from OSM
For my landscape (25 x 18 tiles) I need 7200 c3d files, one for each patch. At the first step for each patch is a mtl and an obj file to import from OSM. Runtime netto are round about 1 -2 days, but there were some errors (see below). So I didn't got the files for 12 patches. That is a good quota, nevertheless will these patches look not good, but first you have to find them while flying (0,16 % of the area). If there are only a few buildings, you will not see it, but in one patch were more than 25000 buildings, if this patch is a part of a bigger town it will be good visible.
The import to Condor
If you import a lot of files into Condor via LE, it will crash. If that happens, it says, that it can't import a filename. If you click OK it continues until the next file were it crashes. My solution for that is:
When the first message appears, kill LE via taskmanager, copy then all c3d files from working\autogen to autogen and delete (or backup) the mtl and obj files for the created c3d files. Start then LE and continue importing. If you don't delete the mtl and obj files from working\autogen, the import will create the c3d files again. The crash happens due to less memory. It happens after creating 500 - 1000 c3d files
Ressources
My landscape has a size of 6 - 7 GB, the autogen files are nearly 20 GB, that is a very big difference. It would be nice, if missing autogen files will not be calculated as cheating, then everybody can decide, if 7 GB is enough or if he/she will use 27 GB for the same landscape in a nicer version
OSM errors
I found three different errors. Is there an update for the python file, or has someone made a workaround? I guess that bad data is the main reason for the errors, so maybe it's possible to ignore the bad buildings and install the good ones. In my example with 25000 buildings you will not see if 1000 are missing, but missing all will be a big hole.
If someone is interested, I can send the h999999.obj and h999999.txt files from working\heightmaps to the patches where the errors occurred.
Error 1, the main error with 10 patches
Error 2, only one patch. A memory error, occurred after a reboot too
Error 3, only one patch
I made this landscape primary for myself, but if someone is interested, I can share it. It's the first landscape I made 3 years ago, NorthGermany, from the Netherlands to Poland, and from Denmark to Göttingen. Tonight I will fly on it the first time.
Thanks again for this very great tool
The tool
The description is good, I followed it word by word and got it to run with the first try, I don't see a point in it worth to make it better.
The import from OSM
For my landscape (25 x 18 tiles) I need 7200 c3d files, one for each patch. At the first step for each patch is a mtl and an obj file to import from OSM. Runtime netto are round about 1 -2 days, but there were some errors (see below). So I didn't got the files for 12 patches. That is a good quota, nevertheless will these patches look not good, but first you have to find them while flying (0,16 % of the area). If there are only a few buildings, you will not see it, but in one patch were more than 25000 buildings, if this patch is a part of a bigger town it will be good visible.
The import to Condor
If you import a lot of files into Condor via LE, it will crash. If that happens, it says, that it can't import a filename. If you click OK it continues until the next file were it crashes. My solution for that is:
When the first message appears, kill LE via taskmanager, copy then all c3d files from working\autogen to autogen and delete (or backup) the mtl and obj files for the created c3d files. Start then LE and continue importing. If you don't delete the mtl and obj files from working\autogen, the import will create the c3d files again. The crash happens due to less memory. It happens after creating 500 - 1000 c3d files
Ressources
My landscape has a size of 6 - 7 GB, the autogen files are nearly 20 GB, that is a very big difference. It would be nice, if missing autogen files will not be calculated as cheating, then everybody can decide, if 7 GB is enough or if he/she will use 27 GB for the same landscape in a nicer version
OSM errors
I found three different errors. Is there an update for the python file, or has someone made a workaround? I guess that bad data is the main reason for the errors, so maybe it's possible to ignore the bad buildings and install the good ones. In my example with 25000 buildings you will not see if 1000 are missing, but missing all will be a big hole.
If someone is interested, I can send the h999999.obj and h999999.txt files from working\heightmaps to the patches where the errors occurred.
Error 1, the main error with 10 patches
Code: Select all
Error: Python: Traceback (most recent call last):
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\CondorOSMImporter.py", line 1243, in execute
ImportOSMData()
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\CondorOSMImporter.py", line 765, in ImportOSMData
bpy.ops.blosm.import_data()
File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\modules\bpy\ops.py", line 109, in __call__
ret = _op_call(self.idname_py(), kw)
RuntimeError: Error: Python: Traceback (most recent call last):
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\__init__.py", line 225, in execute
return self.importOsm(context)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\__init__.py", line 324, in importOsm
a.render()
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\app\blender.py", line 442, in render
m.render()
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\building\manager.py", line 81, in render
self.renderer.render(building, self.data)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\building2\renderer.py", line 156, in render
action.do(building, itemClass, buildingStyle, self)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\__init__.py", line 93, in do
self.generateVolume(footprint, element.getData(self.data))
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\__init__.py", line 100, in generateVolume
volumeGenerator.do(footprint, coords)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\roof.py", line 83, in do
self.render(footprint, roofItem)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\roof_hipped.py", line 70, in render
ok = self.generateRoof(footprint, roofItem, firstVertIndex)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\roof_hipped.py", line 225, in generateRoof
polygonize(
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\lib\bpypolyskel\bpypolyskel.py", line 1048, in polygonize
embedding = graph.circular_embedding(verts,'CCW')
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\lib\bpypolyskel\poly2FacesGraph.py", line 60, in circular_embedding
ordering = sorted(neighbors, key = cmp_to_key( lambda a,b: compare_angles(vList,a,b,vertex)) )
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\lib\bpypolyskel\poly2FacesGraph.py", line 60, in <lambda>
ordering = sorted(neighbors, key = cmp_to_key( lambda a,b: compare_angles(vList,a,b,vertex)) )
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\lib\bpypolyskel\poly2FacesGraph.py", line 18, in compare_angles
a1 = pseudoangle(vList[p1] - vList[center])
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\lib\bpypolyskel\poly2FacesGraph.py", line 11, in pseudoangle
p = d[0]/(abs(d[0])+abs(d[1])) # -1 .. 1 increasing with x
ZeroDivisionError: float division by zero
Location: C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\modules\bpy\ops.py:109
Code: Select all
Error: Python: Traceback (most recent call last):
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\CondorOSMImporter.py", line 1243, in execute
ImportOSMData()
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\CondorOSMImporter.py", line 765, in ImportOSMData
bpy.ops.blosm.import_data()
File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\modules\bpy\ops.py", line 109, in __call__
ret = _op_call(self.idname_py(), kw)
RuntimeError: Error: Python: Traceback (most recent call last):
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\__init__.py", line 225, in execute
return self.importOsm(context)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\__init__.py", line 324, in importOsm
a.render()
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\app\blender.py", line 442, in render
m.render()
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\building\manager.py", line 81, in render
self.renderer.render(building, self.data)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\building2\renderer.py", line 156, in render
action.do(building, itemClass, buildingStyle, self)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\__init__.py", line 65, in do
self.volumeGeneratorMultiHipped.do(footprint)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\roof_flat_multi.py", line 14, in do
self.render(footprint, roofItem)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\roof_hipped_multi.py", line 49, in render
ok = self.generateRoof(footprint, roofItem, firstVertIndex)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\roof_hipped_multi.py", line 130, in generateRoof
polygonize(
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\lib\bpypolyskel\bpypolyskel.py", line 999, in polygonize
skeleton = skeletonize(edgeContours)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\lib\bpypolyskel\bpypolyskel.py", line 855, in skeletonize
(arc, events) = slav.handle_edge_event(i)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\lib\bpypolyskel\bpypolyskel.py", line 344, in handle_edge_event
for vertex in list(lav):
MemoryError
Location: C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\modules\bpy\ops.py:109
Code: Select all
Error: Python: Traceback (most recent call last):
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\CondorOSMImporter.py", line 1243, in execute
ImportOSMData()
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\CondorOSMImporter.py", line 765, in ImportOSMData
bpy.ops.blosm.import_data()
File "C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\modules\bpy\ops.py", line 109, in __call__
ret = _op_call(self.idname_py(), kw)
RuntimeError: Error: Python: Traceback (most recent call last):
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\__init__.py", line 225, in execute
return self.importOsm(context)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\__init__.py", line 324, in importOsm
a.render()
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\app\blender.py", line 442, in render
m.render()
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\building\manager.py", line 81, in render
self.renderer.render(building, self.data)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\building2\renderer.py", line 156, in render
action.do(building, itemClass, buildingStyle, self)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\__init__.py", line 93, in do
self.generateVolume(footprint, element.getData(self.data))
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\__init__.py", line 100, in generateVolume
volumeGenerator.do(footprint, coords)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\roof.py", line 83, in do
self.render(footprint, roofItem)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\roof_profile.py", line 680, in render
slotR.trackUp(roofItem, 0)
File "C:\Users\pklett\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\blosm\action\volume\roof_profile.py", line 465, in trackUp
index += 1 if reflection is False else 2
TypeError: unsupported operand type(s) for +=: 'NoneType' and 'int'
Location: C:\Program Files\Blender Foundation\Blender 4.0\4.0\scripts\modules\bpy\ops.py:109
I made this landscape primary for myself, but if someone is interested, I can share it. It's the first landscape I made 3 years ago, NorthGermany, from the Netherlands to Poland, and from Denmark to Göttingen. Tonight I will fly on it the first time.
Thanks again for this very great tool
Visit https://www.baleit.no
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
- wickid
- Posts: 3253
- Joined: Mon Dec 04, 2006 7:32 pm
- Location: Venlo, NL
- Contact:
Re: OSM first try
The issue is that we use a 3th party addon in Blender called BLOSM to create the building meshes. It is indeed bad data in the OSM database. Unfortunately I don't have the Phyton skills to fix this very complicated bit of code. I only wrote the Blender plugin that populates the BLOSM plugin with all the data from Condor and saves the files to the correct location. There is no easy fix unfortunately
Glad you like the tools and the documentation.
The autogen cannot be removed as it will give an unfair advantage to players that have it removed. You can cross ridges lower, and fly the final glide flatter when there are no buildings in the way. Same reason the tree density setting was changed to a tree visibility distance.

Glad you like the tools and the documentation.
The autogen cannot be removed as it will give an unfair advantage to players that have it removed. You can cross ridges lower, and fly the final glide flatter when there are no buildings in the way. Same reason the tree density setting was changed to a tree visibility distance.
PH-1504, KOE
Condor beta team/Plane developer
Condor beta team/Plane developer
-
- Posts: 1420
- Joined: Tue Aug 25, 2020 7:07 am
Re: OSM first try
Thanks for your fast answer. Even if nothing can/will be changed, it's a very nice piece of software. Here some quick finds to show what it produces. It will need years to look at all the millions of buildings
industry
a church in Helmstedt, didn't expected that
Hamburg (in bad picture quality because of the size restrictions here)
You see me enthusiastic ...
industry
a church in Helmstedt, didn't expected that
Hamburg (in bad picture quality because of the size restrictions here)
You see me enthusiastic ...

Visit https://www.baleit.no
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
-
- Posts: 1420
- Joined: Tue Aug 25, 2020 7:07 am
Re: OSM first try
Now the difficulties begin, I have to edit an obj file. I'm working without any success 3 hours on that, googled a lot, but I'm stucking.
First I imported the obj file. To navigate in the object is strange, to say it in a kind way. But ok, I see the wrong thing I only want to delete (the long "building" red marked).
I choose box select, make a small box on top and a lot of other points of that object are selected too. To select only that line seems to be impossible. But ok, I delete all marked objects, the line is gone and some of the little points (would like to take a better look on it, but if I zoom in, the object dissappears, moving the whole screen seems not possible, oh I hate such software, what did they smoke when they build it ...).
After deleting that line and the other points, I exported the object, got a new obj and mtl file. Renamed them to the name, Condor needs and tried export autogen c3d from obj in LE. LE says it can't export it.
I don't understand that, but it can't be so difficult ... Even if I deleted too much, importing the obj, modifying it and exporting again, Condor doesn't like it. Is there a special way to export for Condor?
Thanks for any help. I know I'm not stupid, but such "solutions" make me feeling stupid
First I imported the obj file. To navigate in the object is strange, to say it in a kind way. But ok, I see the wrong thing I only want to delete (the long "building" red marked).
I choose box select, make a small box on top and a lot of other points of that object are selected too. To select only that line seems to be impossible. But ok, I delete all marked objects, the line is gone and some of the little points (would like to take a better look on it, but if I zoom in, the object dissappears, moving the whole screen seems not possible, oh I hate such software, what did they smoke when they build it ...).
After deleting that line and the other points, I exported the object, got a new obj and mtl file. Renamed them to the name, Condor needs and tried export autogen c3d from obj in LE. LE says it can't export it.
I don't understand that, but it can't be so difficult ... Even if I deleted too much, importing the obj, modifying it and exporting again, Condor doesn't like it. Is there a special way to export for Condor?
Thanks for any help. I know I'm not stupid, but such "solutions" make me feeling stupid

Visit https://www.baleit.no
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
-
- Posts: 735
- Joined: Mon Nov 16, 2009 10:34 am
Re: OSM first try
First of all, looks like your object is sideways, make sure you select the right axis for up and forward when importing the object file (it's among the options in the import dialog).
You have 3 modes which chooses what you select. Keypress 1 is points, Keypress 2 is lines, and Keypress 3 is faces. Try another one and see if it's easier to select what you want. Also try from another angle. Often it can be useful to see an object straight from the top (7 key on numpad, assuming you've imported it with the right axis as up).
Try pressing . (dot) on the numpad, that will zoom into whatever is selected. Panning in default setup I believe is pressing middle mouse button and moving mouse.(would like to take a better look on it, but if I zoom in, the object dissappears, moving the whole screen seems not possible)
Yeah, I've been having trouble converting exported autogen objects if I edit them too. So I've been using the Object Editor (included with landscape toolkit), to manually convert to c3d if I've edited an autogen file.After deleting that line and the other points, I exported the object, got a new obj and mtl file. Renamed them to the name, Condor needs and tried export autogen c3d from obj in LE. LE says it can't export it.
-
- Posts: 1420
- Joined: Tue Aug 25, 2020 7:07 am
Re: OSM first try
Thanks a lot for your hints. The object was sideways because I used a lot of buttons to get it visible 
I tried Object editor before too, did it again but get this message (same like at the first try)
The only line with this characters in the obj file is
usemtl Material
f 1/1/1 5/2/1 7/3/1 3/4/1
When I looked into the obj file, I saw this head line, the name of the mtl file was wrong. But no changes after correcting that
# Blender 4.0.2
# www.blender.org
mtllib o066008.mtl

I tried Object editor before too, did it again but get this message (same like at the first try)
The only line with this characters in the obj file is
usemtl Material
f 1/1/1 5/2/1 7/3/1 3/4/1
When I looked into the obj file, I saw this head line, the name of the mtl file was wrong. But no changes after correcting that
# Blender 4.0.2
# www.blender.org
mtllib o066008.mtl
Visit https://www.baleit.no
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
-
- Posts: 1420
- Joined: Tue Aug 25, 2020 7:07 am
Re: OSM first try
oh, I see in the original file is a very different format
Original
usemtl Material
v 1.36156964 -0.88511240 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.62500000 0.50000000
v 1.36157680 1.11488760 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.87500000 0.50000000
v -0.63842314 1.11489487 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.87500000 0.75000000
f 1/1/1 2/2/2 3/3/3
v 1.36156964 -0.88511240 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.62500000 0.50000000
v -0.63842314 1.11489487 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.87500000 0.75000000
v -0.63843042 -0.88510519 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.62500000 0.75000000
f 4/4/4 5/5/5 6/6/6
New file
usemtl Material
f 1/1/1 5/2/1 7/3/1 3/4/1
f 4/5/2 3/4/2 7/6/2 8/7/2
f 8/8/3 7/9/3 5/10/3 6/11/3
f 6/12/4 2/13/4 4/5/4 8/14/4
f 2/13/5 1/1/5 3/4/5 4/5/5
f 6/11/6 5/10/6 1/1/6 2/13/6
o o066008
v 1.361570 -0.885112 1.000000
v 1.361577 1.114888 1.000000
v -0.638423 1.114895 1.000000
v 1.361570 -0.885112 1.000000
v -0.638423 1.114895 1.000000
v -0.638430 -0.885105 1.000000
v -0.638430 -0.885105 -1.000000
v -0.638430 -0.885105 1.000000
v -0.638423 1.114895 1.000000
v -0.638430 -0.885105 -1.000000
v -0.638423 1.114895 1.000000
v -0.638423 1.114895 -1.000000
v -0.638423 1.114895 -1.000000
v -0.638423 1.114895 1.000000
v 1.361577 1.114888 1.000000
v -0.638423 1.114895 -1.000000
Original
usemtl Material
v 1.36156964 -0.88511240 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.62500000 0.50000000
v 1.36157680 1.11488760 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.87500000 0.50000000
v -0.63842314 1.11489487 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.87500000 0.75000000
f 1/1/1 2/2/2 3/3/3
v 1.36156964 -0.88511240 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.62500000 0.50000000
v -0.63842314 1.11489487 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.87500000 0.75000000
v -0.63843042 -0.88510519 1.00000000
vn 0.00000000 0.00000000 1.00000000
vt 0.62500000 0.75000000
f 4/4/4 5/5/5 6/6/6
New file
usemtl Material
f 1/1/1 5/2/1 7/3/1 3/4/1
f 4/5/2 3/4/2 7/6/2 8/7/2
f 8/8/3 7/9/3 5/10/3 6/11/3
f 6/12/4 2/13/4 4/5/4 8/14/4
f 2/13/5 1/1/5 3/4/5 4/5/5
f 6/11/6 5/10/6 1/1/6 2/13/6
o o066008
v 1.361570 -0.885112 1.000000
v 1.361577 1.114888 1.000000
v -0.638423 1.114895 1.000000
v 1.361570 -0.885112 1.000000
v -0.638423 1.114895 1.000000
v -0.638430 -0.885105 1.000000
v -0.638430 -0.885105 -1.000000
v -0.638430 -0.885105 1.000000
v -0.638423 1.114895 1.000000
v -0.638430 -0.885105 -1.000000
v -0.638423 1.114895 1.000000
v -0.638423 1.114895 -1.000000
v -0.638423 1.114895 -1.000000
v -0.638423 1.114895 1.000000
v 1.361577 1.114888 1.000000
v -0.638423 1.114895 -1.000000
Visit https://www.baleit.no
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
-
- Posts: 735
- Joined: Mon Nov 16, 2009 10:34 am
Re: OSM first try
When you export from Blender make sure you use the correct options, this works for me:
Select: "Apply modifiers", "UV Coordinates", "Normals", "Triangulated Mesh", "Materials Export".
Just guessing, as I don't know the obj format, but my guess is "f 1/1/1 5/2/1 7/3/1 3/4/1" is a line for a face with 4 vertices. If you check the lines starting with f in the original file it has 3 sets of numbers, not 4 like yours. Which means yours has not been triangulated. Condor expects all faces to have 3 vertices. So make sure "Triangulated Mesh" is turned on in the obj export options.
Select: "Apply modifiers", "UV Coordinates", "Normals", "Triangulated Mesh", "Materials Export".
Just guessing, as I don't know the obj format, but my guess is "f 1/1/1 5/2/1 7/3/1 3/4/1" is a line for a face with 4 vertices. If you check the lines starting with f in the original file it has 3 sets of numbers, not 4 like yours. Which means yours has not been triangulated. Condor expects all faces to have 3 vertices. So make sure "Triangulated Mesh" is turned on in the obj export options.
- wickid
- Posts: 3253
- Joined: Mon Dec 04, 2006 7:32 pm
- Location: Venlo, NL
- Contact:
Re: OSM first try
There is a patch viewer option in the toolkit to edit autogen files. It is also described in the manual. It imports and exports in the correct format.
PH-1504, KOE
Condor beta team/Plane developer
Condor beta team/Plane developer
-
- Posts: 1420
- Joined: Tue Aug 25, 2020 7:07 am
Re: OSM first try
Thank you very much for your explanations, I will keep it in mind if I need itarneh wrote: ↑Fri Jan 24, 2025 7:21 amWhen you export from Blender make sure you use the correct options, this works for me:
Select: "Apply modifiers", "UV Coordinates", "Normals", "Triangulated Mesh", "Materials Export".
Just guessing, as I don't know the obj format, but my guess is "f 1/1/1 5/2/1 7/3/1 3/4/1" is a line for a face with 4 vertices. If you check the lines starting with f in the original file it has 3 sets of numbers, not 4 like yours. Which means yours has not been triangulated. Condor expects all faces to have 3 vertices. So make sure "Triangulated Mesh" is turned on in the obj export options.
Of course I read it when I went through the manual the first time after C3 release, but forgot about it now when I needed it. Without the 3 hours of unsuccessful poking in Blender yesterday I wouldn't be able to understand what to do, but today it only took me 5 minutes to delete the wrong building (and some others, but you won't see them missing) and to generate the c3d file via LE.
Thank you both so much, you made my day!
The tower is gone ...
Visit https://www.baleit.no
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
-
- Posts: 1420
- Joined: Tue Aug 25, 2020 7:07 am
Re: OSM first try
After the successful test with NorthGermany I started now to make C3 versions with buildings from all my landscapes (40 until now), have to create ca. 400.000 c3d files, that will take the whole year or more, but it seems to be worth it. If a 3D-idiot like me can create with a few clicks such impressive landscapes, then it has to be done
(the picture again in bad quality to reduce the size)
There occurred one problem. I wanted to start from JFK airport, but got a not working elevator. I guess it's from the cheating protection. Start from La Gardua was no problem. I created the OHA file again without success. What else can I do if I get such a problem?
Maybe it was the same problem Claraflies1 got with the AS32 -> https://www.condorsoaring.com/forums/vi ... 29&t=22872
I wanted to start with the SF28 and didn't got speed enough. By random I saw the stick jumping
BTW, had to learn that you can't see the buildings before you created the OHA file

There occurred one problem. I wanted to start from JFK airport, but got a not working elevator. I guess it's from the cheating protection. Start from La Gardua was no problem. I created the OHA file again without success. What else can I do if I get such a problem?
Maybe it was the same problem Claraflies1 got with the AS32 -> https://www.condorsoaring.com/forums/vi ... 29&t=22872
I wanted to start with the SF28 and didn't got speed enough. By random I saw the stick jumping
BTW, had to learn that you can't see the buildings before you created the OHA file
Visit https://www.baleit.no
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
- wickid
- Posts: 3253
- Joined: Mon Dec 04, 2006 7:32 pm
- Location: Venlo, NL
- Contact:
Re: OSM first try
There is a check function in the landscape toolkit that flags any corrupt C3D files.
PH-1504, KOE
Condor beta team/Plane developer
Condor beta team/Plane developer
-
- Posts: 1420
- Joined: Tue Aug 25, 2020 7:07 am
Re: OSM first try
Hm, found a "check for missing c3d files" in LE, and a "scenery check" in the folder where LE is stored. Both are not what you mean and both without any error message
Visit https://www.baleit.no
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
Events: Vintage Series 24, The Journey
Landscapes, tools, panels, discussion forum ...
Who is online
Users browsing this forum: No registered users