Latest Contributions by MatthiasBuehler1

Hi ! When street segments meet that have different widths, an additional trapezoid shape is inserted to compensate. Those shapes usually create unrealistic models of streets, since lanes would be merging in real world. But the UVs are stretched in that region and the first edge of that geometry is angled, so in CE there's no solution for this issue. The best you can do is avoid streets with different widths. So that's an unsolved issue in 2012. But we've been working on the street system for 2013. Though I'm not perfectly sure if this specific issue will be adressed. Ok so far ? m. ... View more

Hi, Which precise version of CE are you running ? Did you update the graphics driver to the latest version ? I'm not perfectly sure what the issue could be .. Let's track this down ! Matt ... View more

Hi ! Please contact Esri Japan or http://www.crescentinc.co.jp/ Crescent inc created some traditional japanese buildings with CityEngine: http://www.youtube.com/watch?v=00WufWu7GFg ok ? matt ... View more

Hi ! That's the same, just different terminology. ok ? m. ... View more

Hi Helen, Can you PM me your mail address, would be more efficient to discuss this. Let me know.. Matt ... View more

Hi ! That seems to be a rendering issue ( the 3d viewport uses OpenGL to display the geometries ). So I'd say this is unrelated to your export. Can you : 1] delete the log with the fat red 'x' 2] restart CE 3] re-export And check if the error remains ? Lemme know. matt ... View more

Hi ! I'm not sure about this precise projection. There's some (rare) ones which are not supported indeed, but I'm not sure if it's possible to create such a list. Thus I usually recommend to use the default UTM projection. Let me know if reprojecting works for you .. Matt ... View more

Hi, I hope I get your answer soon ! matt ... View more

yay ! *dancie* glad it works now. 😮 ... View more

hi ! I have not checked the new files since usually, there's more files, e.g. the 'world' file, which is also needed for correct placement. Using -georeferenced data is tricky. I'd recommend the following 2 things: 1] What I usually do : - Import the .osm file. This usually works without issues. - Zoom to the data with 'f' - Drag and drop the texture file ( e.g. tif or jpg ) into the viewport, this triggers the terrain import dialog - The size is set to the terrain's resolution, which is of course false in most cases, hit ok to create the terrain - Select the terrain layer and use the w,e keys to move / scale the terrain to the correct spot ( eyeballing ). This usually is by far enough precise 2] If you have ArcGIS available - Import osm into ArcGIS - create basemap in the correct projection - export the extent of interest as GeoTif. This will produce all the right metadata stuff. Ok ? Matt ps. sorry for the inconvenience, but the metadata needs to be spot-on correct, otherwise the system is missing some info. ... View more

Hi Lee ! Open the .mtl in a text editor and check all texture paths (use 'notepad++' to search & replace over many files if needed). Usually if you want the .mtl right next to the .obj file, use a 'relative path', means just use the texture name. E.g. If the path in the .mtl is : mapKd C:/images/myPic.jpg CE cannot find that path because it needs to reside within CityEngine's workspace. If the files are copied to : assets/.. it should work with just the texture name. * * * Otherwise, you can also use the standard file navigation syntax : ../ # 1 dir up /   # 1 dir below * * * I usually create: assets/trees/.. assets/cars/.. .. and within those just use relative paths in the .mtls. Additionally, you'll make your life easier if none of any textures you use in your full projects share the same name because on export, they may ( depending on your export settings ) be copied into 1 big folder. Note that files will not be overridden if they have the same name, but incrementally renamed, which may mess up your workflow. Cheers ! Matt ... View more

Hi, Cool ! Looking good ! 🙂 About the second floor : Very easy: on each shape of each floor, create an attribute with the actual height above floor Even though that if you import the shapes they're at 0 height. then, in your code, initialize the attr and use it to directly translate the shape up. e.g. attr shapeElevation = 0 # points to object attr with e.g. 2.88 m height @StartRule Shape -->     alignScopeToAxes(y)     t(0, shapeElevation, 0)     DoYourStuff. Ok ? ... View more

Hi, I've been able to import the points, so no worries there. The shapes are true circles, so no polygonal shapes. I'm not perfectly sure, but I guess that's not supported yet. Try converting the circles to polygonal shape features, ok ? Matt ... View more

Hi, The toolbox relies on the Data Interoperability extension from Safe software. But preparing those raster files should not be an issue and should not need that. Do you use the projection metadata files ( .prj, .world, .. ) ? Also, can it be that your satellite picture has an alpha channel ( transparency ), which would prevent it's display ? Let me know.. Matt ... View more