Site Tools
ToolsShow pagesourceOld revisionsRecent ChangesMedia ManagerSitemapLogin with RhinoAccountsRegister&
Fixing Bad Objects
How to find and (hopefully) fix bad objects created by Rhino, or by importing from other programs
I’ve got a bad object. Why did that happen and how do I fix it?
What is a bad (invalid) object?
“Bad” objects in Rhino are ones that either violate certain
rules, or have a structural problem.
In theory, Rhino does not produce bad objects, but in practice, it is possible and does happen periodically.
Once you know how to deal with them, they don’t usually take too much to fix.
Most often, the bad objects are surfaces, but bad curves also happen occasionally as well.
How do I know if I've got one?
The simplest way to find bad objects is to use the command SelBadObjects (Analyze&Diagnostics&Select Bad Objects).
All invalid objects will be selected.
But a polysurface may be bad if it contains only one bad surface.
You can figure out which one by using the command ExtractBadSrf (not in the menus), which will extract the bad surfaces and select them.
There is a useful command in Rhino called CheckNewObjects, which turns on checking in the background and checks all objects as they are created or imported.
This way you know immediately when there’s a problem.
Well, there are many technical explanations.
With surface objects, often it is the structure of the trim curve that is bad. It can have one or more segments that are microscopic and this causes problems.
Other times a surface can be bad because it has either two or more rows of control points on top of each other, or has a zero length in one direction (a collapsed edge).
This situation is easy to produce in Rhino V3: make a vertical plane or line and then project it to the Cplane from the Top View.
The object now has zero length in one direction and will be considered bad.
In Rhino V4, this type of operation has been disallowed in certain cases, so that you will not get a bad object. The command will simply fail and you will get an error message.
Yet, it is still possible to produce bad objects in V4.
Why might a surface trim curve be bad?
You probably didn’t intentionally make it so.
Bad objects often show up after using Join (or some other command that also joins objects, like Booleans). When joining objects, Rhino often needs to split edges and adjust trim curves.
In certain situations parts of these split edges can end up being microscopic. Or the adjustment of the trim curve goes wrong and all of a sudden Bing!! you have a bad object.
(By the way, when I say “microscopic” I mean smaller than your absolute tolerance. Objects that are smaller than that generally have no business in your file and will cause problems.)
Bad objects on import/export
Importing geometry from other programs can also produce bad objects.
If you are running CheckNewObjects, while a file is importing you will get a message if and when an invalid object has been created.
You need to click OK to acknowledge each one.
If there are many, this can be annoying. You can turn the command off and restart it after the import is done.
It is important to understand that the imported objects were likely not considered bad in
the originating program.
Every program has its own way of creating and checking geometry, and those may not be the same as how Rhino goes about it.
On top of that, exchanging data between programs that have different formats requires at least one translation and sometimes two (via a neutral format such as IGES). Translation problems can cause bad objects, depending on the quality of the import/export functions.
Rhino will also produce objects that it does not consider bad, but are flagged as bad by other programs.
Phantom surfaces
Why can't I see my bad object?
Occasionally, Rhino produces surfaces that are bad, but you can't see them.
Literally, they are invisible!
(They are invisible because no render mesh was able to be produced to display them.) They are sometimes referred to as phantom surfaces.
Phantom surfaces can cause files to act oddly, for example a ZoomExtents that doesn't work correctly because the invisible surface is out in space and the Zoom command is taking it into account.
These can usually be selected with SelBadObjects, and the best thing is to simply use Delete to get rid of them. Often they can't be fixed.
Sometimes, Delete won't work. If that happens, try Ctrl+X to cut them from the file.
cannot select them in any other way, you can also try this:
Zoom extents, window select everything and use Hide.
Then try a Ctrl+A.
Usually this selects everything in the file, even objects that are unselectable any other way.
If you see on the command line that an object is selected, use What to verify that it is indeed your bad object (it will say “invalid”), then just delete it and show all again.
Bad meshes
If a polygon mesh object rings up as bad, use CheckMesh to see a more detailed report of what is
wrong with it. This command tells you a good deal about what can be fixed, and you may find the commands you need among the offerings in the Mesh menu, under mesh Edit tools and mesh repair tools. Some useful commands are:
ExtractDuplicateMeshFaces
ExtractNonManifoldMeshEdges
CullDegenerateMeshFaces
UnifyMeshNormals
OK, How do I fix bad curves and surfaces?
Bad polycurves are most often fixed by just exploding and rejoining.
Otherwise, look for microscopic segments included in the curve and eliminate those.
If that still doesn't fix things, it may be that something is really wrong with the
knot structure of the curve, and it requires more advanced investigation and reconstruction.
My strategy for dealing with bad surfaces due to trim curves follows. Before starting, determine which are the bad surfaces and hide everything else temporarily (you may need to run ExtractBadSrf as above).
1. First, I usually run the command RebuildEdges on all bad objects. This may fix some. It more or less restores the edges of a surface to the state they were before joining.
But it also means that the surface might no longer join up to its neighbors, or that joining might make it go bad again. But it does work OK in some cases.
If some surfaces are fixed (use SelBadObjects/Invert), hide those.
Sometimes running ShrinkSrf on bad surfaces also helps.
2. Use the Untrim command with the keep trim objects option selected (otherwise known as DetachTrim) on the first bad surface, then, while the trim curve is still selected, use Trim to retrim the surface.
Has this fixed the surface?
If so, good, hide it. If not, leave it and run the same procedure on all other bad surfaces one at a time.
Hide all that go good.
3. If any bad objects are left, run DetachTrim on them again. Explode the resulting trim curve and look for micro segments in the curve somewhere. This is the most common case of bad trims. Look at how many component curves the trim curve has. Often there will be a suspicious number, i.e. what looks like it should be a rectangle says 5 curves not 4. Somewhere in there is a micro curve that is messing things up. Often it's near a corner. Try window selecting near the ends of your trim curve segments. Or, use the command SelShortCrv and set a small value.
If you find some microsegments, delete them and rejoin the trim curves into a closed loop. Retrim the surface with it. This usually fixes pretty much everything that isn’t fixed by other methods.
4. Last, try unhiding everything (Show), and see if you can join all up without having objects go bad again.
If all joins up well and no bad objects, great!
If not, then it’s generally because Join is trying to force things together that don’t fit correctly.
In that case you have to analyze the surfaces that are going bad and the relation with their neighbors to try and find out what doesn’t fit and why.
This can sometimes take some pretty close looking and head scratching…
Note: The above methodology is for dealing with surfaces with bad trim curves.
It won’t help surfaces with collapsed edges or stacked rows of control points.
Those need to be dealt with by other methods such as knot removal or just plain reconstruction.
Surfaces with collapsed edges are easy to spot – the display looks like a curve, but in Properties it says it’s a surface.
In general just delete these.
Page Tools
& &McNeel &lumion2.5我安装破解后怎么还是有login啊_lumion吧_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0成为超级会员，使用一键签到本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：47,459贴子：
lumion2.5我安装破解后怎么还是有login啊收藏
我卸了 重新安装破解怎么还是这样
【唐国强再饰诸葛亮】《神道三国》今日公测领豪礼！ 抢看新三国剧情！
我的也是，，，怎么办，，，
你没破解成功
没破解成功吧
Lumion2_5-1a.bin
和 Lumion2_5-1b.bin
这两个文件好像没用到
我也是这问题求解，帮帮我嘛
自己看吧，绝对可以，我已经在用了
加我我帮你破解
我是2.5的版本
破解的时候有一个文档会有破解流程，有一步是让你在c盘里新建一个文件夹
并命名为Lumion 2 注意Lumion 与
之间有个空格哦
必须要有个空格
你出现login就是他的问题
「BIM企业实训」lumion考试上海报名点/考点,就在「交大」!一考三证,人社部证书\中国图学学会证书\交大证书,高含金量,详询
你没有破解
lumion2.5破解之后打开出现could not connect.er 求解答
我也遇到过，主要的问题还是在于整个破解过程的注意！在未破解完成之前一定不要运行lumion软件！！！第一步，在hosts里面加入地址；第二步新建lumion 2文件夹（如果担心自己会命名错误，你直接从说明里面复制那个名字过来就是了嘛）；第三步，把文件进这个文件夹，并把权限改为administrator；第四部就是打开破解软件破解了，如果全部成功，就都会是done （当然了，如果你的杀毒软件误报的话，也请点击允许，祝你好运）
问一下高手：我的2.5所有破解步骤都有了，但还是不成功，之前装过4.0.2，所以hosts文件已经加过地址，对比了下，两个是一样的所以没改，这个有影响吗？还有4.0.2电脑运行不是很好，换2.5会不会好点？
想问你，解决了没？我的也这样
楼楼，有没有安装包，谢谢了
看看你lumion 2建文件夹的时候名字有没有拼错
想不通6.0破解那么好用，为什么都来搞25版本？难道25有什么特别的地方吗
登录百度帐号推荐应用Access denied |
used Cloudflare to restrict access
Please enable cookies.
What happened?
The owner of this website () has banned your access based on your browser's signature (3cd24-ua98).Lumion2.5下载、安装、破解和相关教学资源
一、看完这三套教程基本可以掌握lumion了：
1、Ma5老师的教程：&&
2、火星时代视频教程区，王显旺老师的教程&&
3、优酷网的官网教程（有含中文语音的），自己搜吧。
文件是直接使用早上吧里发的破解器中的，破解器是默认为安装在C盘，现在只需要覆盖就行，文件小很多，也不用担心病毒等问题；我的电脑是64位系统，因此这里只发64位版本的文件
压缩包内的文件是两个，一个是破解文件，一个是原始文件。
————————————————————————————
二、安装和破解
破解流程：
步骤一：在C:\ProgramData\路径下创建Lumion 2文件夹，如果有就不用创建。
步骤二：复制myLumion.ppp文件到刚才创建的文件夹中。
步骤三：复制Channels文件夹下的三个文件直接覆盖软件安装的相应目录（如D:\Program Files\Lumion
2.5\Channels）
步骤四：编辑HOSTS文件（C:\Windows\System32\drivers\etc）
&&&添加以下两段地址（如果有防火墙的话，可以在防火墙中设置屏蔽lumion程序访问网络就可以）
&&&127.0.0.1
&&&127.0.0.1
&&&保存并关闭HOSTS就可以使用了！
注：激活无效的情况下从新安装lumion2.5一帮可以解决
&&某些360安全卫士等软件会导致破解后运行出错，这是吧友“四圣兽“的血泪史&
论坛中的PRO破解说明是适用于windows
7的（亲测32和64都没有问题），使用XP的朋友可能会发现什么“C:\ProgramData\路径”我根本没有啊，坑爹了，安装好之后还要输入用户名和密码。
放心不用重装系统，神是不会抛弃XP的，没装过lumion2的朋友只要在C:\Documents
and Settings\All Users\Application Data下新建文件夹“lumion
2",将myLumion.ppp文件复制到里面去（装过的直接复制替换），一切搞定，快点体验一下2.5PRO版吧（其实和2.2差别不大，几个专享功能的作用并不明显，水面反射、材质透明度、镜面反射都没有解决，不要拿砖拍我）。另求汉化补丁和乱码补丁（32和64位的都可以），特效文字乱码从2.2开始就这样了，请好心人发到。
————————————————————————————————————————————————————
原地址：/forum.php?mod=viewthread&tid=53469&extra=page=1&page=1&
现在一步一步教大家破解2.5 pro旗舰版，保证教会
首先准备材料（2.5的安装包&&破解补丁-后面会提供给大家&&还要有一台好使的电脑）
1.安装lumion2.5的安装包，这步应该没有问题吧，等待安装结束。（见图1）&
2.安装破解补丁，我提供的破解补丁，解压后放在一边备用。我们先来到C盘主目录下（见图2）&
3.在文件夹选项里选择“显示隐藏的文件夹”，点击进入（见图3）&
4.在“查看”中选择“显示隐藏的文件”，点击应用（见图4）&
5.在c盘根目录找到隐藏的ProgramData文件夹，双击进入，嗯离成功不远了~&（见图5）&
6.在ProgramData文件夹下新建一个文件夹，命名为Lumion
2（注意字母和数字之间的空格）（见图6）&
7.将破解文件copy到Lumion 2文件夹下，具体说明（见图7）&
8.用行破解文件，点击“patch”，嘿嘿，还差一步就好了~&（见图8）&
9.来到c盘目录：windows-system32-drivers-etc路径中找到hosts文件，用记事本打开，在最后一行添加
127.0.0.1 &
&之后保存并退出（见图9）&
10.运行Lumion 2.5 ，你将看到，你已经大功告成了 ，lumion可以使用了。
ps：排版不是很友好，希望大家不要见怪，不知道为什么不能一行一图，只能这样了 。
& 如果大家觉得好的话，可以砸宝石给我，嘿嘿&&希望能变成精华&&亲！~
1.32 MB, 下载次数: 76
已投稿到：
以上网友发言只代表其个人观点，不代表新浪网的观点或立场。}