Please post bug reports for 1.1.5 in this thread.
Wings 1.1.5 bug reports
| Author | Comment | ||
|---|---|---|---|
 bjorng |
Wings 1.1.5 bug reports |
Lead | |
|
(07/01/09 01:42:53) |
|
||
|
phrenzy84 |
|||
|
(07/02/09 01:56:17) |
Is it me or is there something really screwy with tweak.
when you move your component it puts the cursor back from where you started. Its really jarring. Tried it on version 1.1 and its doesn't have this problem. hope this helps |
||
 optigon |
|||
|
(07/02/09 07:31:16) |
<<Is it me or is there something really screwy with tweak.
when you move your component it puts the cursor back from where you started. Its really jarring. Tried it on version 1.1 and its doesn't have this problem. hope this helps >> Tweak is at an intermediate stage in this regard. Originally Tweak drag was limited to the size of the geometry window, because the cursor had to always be visible. Now you can drag beyond the limits of the window, which I think is better. There are still some things to sort out though. I'll try and fix this for the next release. |
||
|
Fonte Boa |
|||
|
(07/02/09 07:55:28) |
No, phrenzy84: this was already present at 1.1.
|
||
|
optigon |
|||
|
(07/02/09 08:06:52) |
<<No, phrenzy84: this was already present at 1.1. >>
Well either way, I'm going to do something about this 
|
||
|
Siber |
|||
|
(07/03/09 21:40:24) |
Exporting a mesh to obj that I just imported from obj, after making a quick autosmooth. It fails to export, most bothersomely. The crash dump starts out as
follows(full is 300kb, whee.)
Dump written 2009-7-4_1-36On further examination, this doesn't happen when I do the same procedure to the same model in 1.1.3
Last Edited By: Siber
07/04/09 13:12:21.
Edited 1 times.
|
||
|
zdarby |
Combine Error | ||
|
(07/04/09 14:35:17) |
I have a file that will not combine after being separated.
I don't know why. I've yet to find another such file. Here is the dump: Dump written 2009-7-4_15-27 Version: 1.1.5 Window: geom Reason: {badarg,[{0,[none|{0.105119,0.460095}]}, {1,[none|{0.206985,0.068651}]}, {1,[none|{0.206985,0.068651}]}, {2,[none|{0.206985,0.068651}]}, {2,[none|{0.206985,0.068651}]}, {3,[none|{0.105119,0.460095}]}, {3,[none|{0.105119,0.460095}]}, {4,[none|{0.206985,0.046821}]}, {4,[none|{0.206985,0.046821}]}, {5,[none|{0.105226,0.407489}]}, {5,[none|{0.105226,0.407489}]}, {6,[none|{0.105226,0.407489}]}, {6,[none|{0.105226,0.407489}]}, {7,[none|{0.422887,0.338412}]}, {7,[none|{0.422887,0.338412}]}, {8,[none|{0.206985,0.068651}]}, {8,[none|{0.206985,0.068651}]}, {9,[none|{0.105119,0.397943}]}, {9,[none|{0.105119,0.397943}]}, {10,[none|{0.206985,0.068651}]}, {10,[none|{0.206985,0.068651}]}, .................]} Stack trace: [{array,from_orddict_1,7}, {array,from_orddict,2}, {wings_va,merge_1,3}, {wings_va,merge,2}, {wings_body,combine,1}, {wings_body,command,2}, {wings_develop,time_command,2}, {wings,raw_command,4}]
Last Edited By: optigon
07/04/09 19:10:15.
Edited 1 times.
|
||
|
deerwood |
picking problem | ||
|
(07/04/09 18:26:53) |
I discovered a picking problem:
In vertex mode; most of the time the correct vertex is highlighted (the pick ray stops at the surface of the model and the nearest vertex of the hit face is marked) but sometimes the pick ray "reaches through" the surface and hits/marks some unwanted vertex. Though this can be spotted by observing the highlight before selecting, it is rather annoying when doing mass manual selections. In the case at hand I was about to mark half of the checkerboard top faces to color them and was surprised to find more then 32 center vertices selected after pointing roughly to the middle and clicking. As I couldn't find a simpler model showing the problem here the model (please respect, that I claim the copyright for the design/idea of a 3D checker board, something I wanted to have since 30 years. Just be fair, please). Not sure, but I believe this prob to be associated with the recent move from OGL picking to Wings picking. Others having similar problems? Best regards |
||
|
optigon |
|||
|
(07/05/09 11:18:40) |
Siber wrote:Thanks for the report, but we need some more information to zero in on the cause. It would be great if the model that caused this were available to download so we could test. Are there holes in the mesh? Normally this wouldn't be a problem but there is a bug in the current version of wings which causes a crash when smooth a model that includes a hole. Any more information about this crash would be helpful. Thanks! |
||
|
Siber |
|||
|
(07/05/09 20:56:33) |
Alrighty. I was reticent because I'm working on this model at the behest of someone else, so I wanted to get their permission before posting the mesh.
Which I have done.
Procedure: Import that obj file, select and autosmooth at 30 degrees, attempt to export back to obj. It will rather not work.
Last Edited By: Siber
07/06/09 11:32:45.
Edited 1 times.
|
||
|
optigon |
|||
|
(07/06/09 06:30:44) |
Thanks, Siber
You can remove the file now if you wish. |
||
|
taraborn |
selecting edges problem? | ||
|
(07/06/09 15:00:43) |
When I try to highlight/select edges (in edge mode with Show Edges ON, other modes that hide the edges such as Smooth Shading OFF, Highlighting Edges in
Preferences is ON too...) it doesn't show neither the highlight (green) nor the selection (red) colors. This doesn't happen with faces, objects or
vertexes; just with edges when they are actually drawn as a black border between the faces.
EDIT: I'm using the Linux version of Wings3D (in Ubuntu). Barring that it works like a charm. |
||
|
no204 |
|||
|
(07/06/09 22:30:55) |
Hi all,
I just found this version is unable to bake the AO. no204.
Last Edited By: no204
07/07/09 00:43:39.
Edited 1 times.
|
||
|
bjorng |
|||
|
(07/07/09 11:43:14) |
Siber,
I found a bug in importing models that don't have UV coordinates on all faces. I have corrected that bug. However, I could not reproduce the crash you reported using your model. (Possibly because I don't have the .mtl file.) I still cannot explain that crash, which is unfortunate because that could be another bug. Can you still reproduce the crash? zdarby, I have fixed the Separate/Combine bug. deerwood, The picking issue is an old issue. I can reproduce it in 1.0.1. Originally, I used depth information returned by OpenGL to find out which face that was nearest. Then it turned out that some OpenGL drivers did not return reliable depth information, so I had to figure out which face was nearest by myself. I didn't want to implement the code for intersecting a ray with a polygon, so I cheated using some heuristics that works most of the time. I am working on a better solution. It is easier now that all selection code is my own. |
||
|
Siber |
|||
|
(07/07/09 15:23:04) |
bjorng: I just tried again, and it's still crashing. A full crash dump can be found at http://files.getdropbox.c.../896078/wings_crash.dump if that would be a help. There is no .mtl file
associated with the .obj to import.
|
||
|
bjorng |
|||
|
(07/07/09 22:08:51) |
Siber wrote: Thanks for confirming that it still crashes. I can reproduce the crash if I enable the Triangulation option, so that explains the mystery. I actually fixed the bug itself yesterday, but it bothered me that I could not reproduce the crash myself so that I could confirm it. |
||
|
MrChristopherSEA |
Distribute in UV not working | ||
|
(07/09/09 21:59:26) |
The Distribute function of the UV editor doesn't seem to be working.
|
||
|
Micheus |
|||
|
(07/10/09 16:56:48) |
It's not necessary a bug because exists from earler versions:
1) When I have a project opened and then I open an other project the camera stay in the last position. Ok I can use CTRL+R to reset cam position, but could be more suitable if the camera position could be preserved for the next access or if not possible to implement, just automaticly reset cam position. 2) When using SHIFT+TAB to view smoothed objects there is a problem that not exists using "Smooth Shading" button (that's work fine at this situation). The properties that I will talk about is on Geometry Graph window (GG):
TIA
Last Edited By: Micheus
07/10/09 17:48:49.
Edited 2 times.
|
||
|
bjorng |
|||
|
(07/11/09 00:32:34) |
Micheus,
1) Automatically saving the camera position in a wings file and restoring it when opening it would certainly be possible. If other users find that the right thing to do, we might implement that. (You might want to post about that in the feature request thread.) 2) I am not sure that we want to fix this. We intentionally overloaded the wireframe state and wireframe hotkeys to keep things simple (both for the implementation and for users). |
||
|
Micheus |
|||
|
(07/11/09 13:15:25) |
bjorng wrote:1) Ok, I will put there. 2) I have mentionade this because some times I'm editing an object surrounded by others objects. I set that objects to wireframe and then I try to view edited object in shaded mode (using the shortcut) by many viewpoints. So, when back to edit the object I have to set again the others objects to wire.... But there is no problem. Although some times this could not be convenient to me I will try to use visible property. Thanks bjorng and congratulation by your great work with Wings3D |
||
