Please remove me from this group!

----- Original Message -----
From: "tobiasasphaug" <tobiasasphaug@...>
To: <meshwork@yahoogroups.com>
Sent: Friday, September 24, 2004 10:13 AM
Subject: [meshwork] novice advice on texturemapping


> my apologies if this is an identical question to a previous one, but my
lingo vocab is too
> poor to detect it.
>
> I'm trying to make a space ship for the excellent Oolite
(http://oolite.aegidian.org/) and
> apply textures as he describes in a tutoral.
>
> I open Meshwork 2.0.1 on my OSX 3.5, and things go well until I 3D preview
my object.
> the textures in almost every instance do not apply themselves in a flat
way according the
> the desired axis, and in many cases neglect to render several planes. the
result looks like
> an object with wrinkled skin missing several sides.
>
> is this a typical newbie fool's mistake?
>
> any advice would be superappreciated.
>
> also, is it only me and my copy that do not enjoy the option of
Apl-Z/undo, or is this a
> missing feature in Meshwork?
>
>
>
> Meshwork Home: http://codenautics.com/meshwork/
> Mailing List:  http://www.egroups.com/group/meshwork/
>
> Yahoo! Groups Links
>
>
>
>
>

my apologies if this is an identical question to a previous one, but my lingo
vocab is too
poor to detect it.

I'm trying to make a space ship for the excellent Oolite
(http://oolite.aegidian.org/) and
apply textures as he describes in a tutoral.

I open Meshwork 2.0.1 on my OSX 3.5, and things go well until I 3D preview my
object.
the textures in almost every instance do not apply themselves in a flat way
according the
the desired axis, and in many cases neglect to render several planes. the result
looks like
an object with wrinkled skin missing several sides.

is this a typical newbie fool's mistake?

any advice would be superappreciated.

also, is it only me and my copy that do not enjoy the option of Apl-Z/undo, or
is this a
missing feature in Meshwork?

>Another question, under OS9 a .3dmf file was (through quicktime?) viewable with
say
>SimpleText, has OSX something alike? Or even better, is there an easy
(preferable non-
>plugin) way to view it in a html-browser?
>
>
>
You can still view 3dmf files (the text variety any way) in OS X.  However, OS X
does some really really irritating automatic inference on files in an effort to
"help" you find the right application opening and reading various kinds of
files.  As an unfortunate result, you often cannot directly drop an obvious text
file onto TextEdit or the like because it fails to believe the file is
compatiable with a text editor.  Sheez!  I hate it.

The solution, which is tedious, is to Get Info on the file and alter the file's
opening application to the program you want, Simpletext, whatever.  Half the
time when you do that, the icon doesn't automatically change appropriately so it
doesn't look like anything is different, but after doing that you should be able
to open the file with a text editor.

The next time you edit the file with a different kind of program, it may revert
however, undoing your fix.

________________________________________________________________________
Keith Wiley                                kwiley@...
http://www.unm.edu/~keithw                 http://www.mp3.com/KeithWiley

"Yet mark his perfect self-contentment, and hence learn his lesson,
that to be self-contented is to be vile and ignorant, and that to
aspire is better than to be blindly and impotently happy."
                                            --  Edwin A. Abbott, Flatland
________________________________________________________________________

> OS9- meshwork-preview looked just plainbetter (no blinking artifacts), is this
> a 'feature'? Quesa's problem? Thinghy under development?

In my experience, OS 9 and OS X render identically when using Quesa, but OS
9 renders significantly better than that when using Quickdraw3D. Higher
frame rates, less "jumpy" lighting, less scissoring of neighboring objects.

lj

Ollah, been putering away for ages with Meshwork, and a tiny observation pops up
when
working with OSX.3.5 and Quesa in relation with the preview under OS9.xx. OS9-
meshwork-preview looked just plainbetter (no blinking artifacts), is this a
'feature'?
Quesa's problem? Thinghy under development?

Another question, under OS9 a .3dmf file was (through quicktime?) viewable with
say
SimpleText, has OSX something alike? Or even better, is there an easy
(preferable non-
plugin) way to view it in a html-browser?

much regards

I am getting frequent crashes when using the Combine Overlaps command.
Sometimes it works, sometimes it doesn't, but when it doesn't it is
reproducable with the same model consistently, thereby preventing me from
making forward progress with my work.  Heres the crash log that it
produces:

**********

Host Name:      dhcp-40.cs.unm.edu
Date/Time:      2004-08-05 13:42:27 -0600
OS Version:     10.3.4 (Build 7H63)
Report Version: 2

Command: Meshwork
Path:    /Users/keithwiley/Programming/quesa/Meshwork/Meshwork
2.0.1/Meshwork
Version: ??? (???)
PID:     24039
Thread:  0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000014

Thread 0 Crashed:
0   Meshwork  0x0042a5b4 DetachEdge__6VertexFP4Edge + 0x44
1   Meshwork  0x0040fbd8 CollapseEdge__8MyWindowFP6VertexP6Vertex +
0x448
2   Meshwork  0x0044b2b0 DoCombine__8MyWindowFP11OperCombine + 0xbb0
3   Meshwork  0x0041a9ec HandleMenuSelection__8MyWindowFss + 0x15c
4   Meshwork  0x00424404 HandleMenuSelection__6AdvAppFss + 0x114
5   Meshwork  0x00409324 HandleMenuSelection__5MyAppFss + 0x54
6   Meshwork  0x00407fec HandleMouseEvent__7MoofAppFR11EventRecord +
0x9c
7   Meshwork  0x00424284 HandleMouseEvent__6AdvAppFR11EventRecord + 0xb4
8   Meshwork  0x00407b28 DispatchEvent__7MoofAppFR11EventRecord + 0x58
9   Meshwork  0x00407a80 GetAndHandleEvent__7MoofAppFl + 0x70
10  Meshwork  0x004078a8 Tick__7MoofAppFv + 0x48
11  Meshwork  0x00407078 main + 0x98

PPC Thread State:
   srr0: 0x0042a5b4 srr1: 0x0200f030                vrsave: 0x00000000
     cr: 0x2400241c  xer: 0x20000000   lr: 0x0040fbd8  ctr: 0x900f60a0
     r0: 0x00000000   r1: 0xbffff340   r2: 0x000bf000   r3: 0x00000000
     r4: 0x017cf1a0   r5: 0x0000001c   r6: 0x017cdba0   r7: 0x017cf47c
     r8: 0x017cdc20   r9: 0x017ec2b0  r10: 0x00000000  r11: 0xa02811f8
    r12: 0x017ccecc  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
    r16: 0x017cce94  r17: 0x017cce94  r18: 0x017e8430  r19: 0x017e8160
    r20: 0x017cf180  r21: 0x017e6a50  r22: 0x00000003  r23: 0x017e6b90
    r24: 0x00000003  r25: 0x00000000  r26: 0x00000000  r27: 0x000c2509
    r28: 0x017cdba0  r29: 0x017cf1a0  r30: 0x017c7d30  r31: 0x00000000

Binary Images Description:
     0x1000 -     0x9fff Meshwork
/Users/keithwiley/Programming/quesa/Meshwork/Meshwork 2.0.1/Meshwork
    0xb6000 -    0xbd833 OpenGLLibrarypwpc  PEF binary:
OpenGLLibrarypwpc
    0xbd840 -    0xbe26b OpenGLUtilitypwpc  PEF binary:
OpenGLUtilitypwpc
   0x287000 -   0x2d29b1 CarbonLibpwpc  PEF binary: CarbonLibpwpc
   0x2d29c0 -   0x2eacad Apple;Carbon;Multimedia  PEF binary:
Apple;Carbon;Multimedia
   0x30f950 -   0x30f9e1 CFMPriv_AGL  PEF binary: CFMPriv_AGL
   0x30fb90 -   0x30fc42 CFMPriv_CoreFoundation  PEF binary:
CFMPriv_CoreFoundation
   0x30fe30 -   0x30fee5 CFMPriv_DVComponentGlue  PEF binary:
CFMPriv_DVComponentGlue
   0x310110 -   0x3101b3 CFMPriv_QuickTime  PEF binary:
CFMPriv_QuickTime
   0x310230 -   0x3102a7 CFMPriv_System  PEF binary: CFMPriv_System
   0x310550 -   0x310620 CFMPriv_CarbonSound  PEF binary:
CFMPriv_CarbonSound
   0x3106a0 -   0x310773 CFMPriv_CommonPanels  PEF binary:
CFMPriv_CommonPanels
   0x310850 -   0x31090b CFMPriv_Help  PEF binary: CFMPriv_Help
   0x310910 -   0x3109da CFMPriv_HIToolbox  PEF binary:
CFMPriv_HIToolbox
   0x310a60 -   0x310b36 CFMPriv_HTMLRendering  PEF binary:
CFMPriv_HTMLRendering
   0x310bb0 -   0x310c83 CFMPriv_ImageCapture  PEF binary:
CFMPriv_ImageCapture
   0x310d10 -   0x310df5 CFMPriv_NavigationServices  PEF binary:
CFMPriv_NavigationServices
   0x310e70 -   0x310f46 CFMPriv_OpenScriptingMacBLib  PEF binary:
CFMPriv_OpenScriptingMacBLib
   0x311020 -   0x3110de CFMPriv_Print  PEF binary: CFMPriv_Print
   0x311100 -   0x3111cd CFMPriv_SecurityHI  PEF binary:
CFMPriv_SecurityHI
   0x311250 -   0x311332 CFMPriv_SpeechRecognition  PEF binary:
CFMPriv_SpeechRecognition
   0x3113b0 -   0x311483 CFMPriv_CarbonCore  PEF binary:
CFMPriv_CarbonCore
   0x311500 -   0x3115d3 CFMPriv_OSServices  PEF binary:
CFMPriv_OSServices
   0x3116b0 -   0x311772 CFMPriv_AE  PEF binary: CFMPriv_AE
   0x311780 -   0x311845 CFMPriv_ATS  PEF binary: CFMPriv_ATS
   0x3118c0 -   0x311997 CFMPriv_ColorSync  PEF binary:
CFMPriv_ColorSync
   0x311a20 -   0x311b03 CFMPriv_FindByContent  PEF binary:
CFMPriv_FindByContent
   0x311b80 -   0x311c5a CFMPriv_HIServices  PEF binary:
CFMPriv_HIServices
   0x311cd0 -   0x311db0 CFMPriv_LangAnalysis  PEF binary:
CFMPriv_LangAnalysis
   0x311e40 -   0x311f26 CFMPriv_LaunchServices  PEF binary:
CFMPriv_LaunchServices
   0x312000 -   0x3120d7 CFMPriv_PrintCore  PEF binary:
CFMPriv_PrintCore
   0x3120e0 -   0x3121a2 CFMPriv_QD  PEF binary: CFMPriv_QD
   0x3122a0 -   0x312389 CFMPriv_SpeechSynthesis  PEF binary:
CFMPriv_SpeechSynthesis
   0x405000 -   0x49805a Meshwork  PEF binary: Meshwork
   0x499000 -   0x55a0fe Quesa  PEF binary: Quesa
0x88eb0000 - 0x88ebcfff com.apple.agl 2.5 (AGL-2.5)
/System/Library/Frameworks/AGL.framework/Versions/A/AGL
0x8be90000 - 0x8be91fff DVComponentGlue
/System/Library/Frameworks/DVComponentGlue.framework/Versions/A/DVComponentGlue
0x8fe00000 - 0x8fe4ffff dyld  /usr/lib/dyld
0x90000000 - 0x90122fff libSystem.B.dylib  /usr/lib/libSystem.B.dylib
0x90190000 - 0x9023dfff com.apple.CoreFoundation 6.3.4 (299.31)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x90280000 - 0x904f9fff com.apple.CoreServices.CarbonCore 10.3.4
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCo\
re.framework/Versions/A/CarbonCore
0x90570000 - 0x905defff com.apple.framework.IOKit 1.3.2 (???)
/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90610000 - 0x9069afff com.apple.CoreServices.OSServices 3.0.1
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServic\
es.framework/Versions/A/OSServices
0x90700000 - 0x90700fff com.apple.CoreServices 10.3 (???)
/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x90720000 - 0x90787fff com.apple.audio.CoreAudio 2.1.2
/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x907f0000 - 0x907f9fff com.apple.DiskArbitration 2.0.3
/System/Library/PrivateFrameworks/DiskArbitration.framework/Versions/A/DiskArbit\
ration
0x90810000 - 0x90810fff com.apple.ApplicationServices 1.0 (???)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationS\
ervices
0x90910000 - 0x90983fff com.apple.DesktopServices 1.2.2
/System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Deskt\
opServicesPriv
0x90c30000 - 0x90c4afff libGL.dylib
/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x90c60000 - 0x90cc2fff libGLU.dylib
/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x90d00000 - 0x90d1bfff com.apple.SystemConfiguration 1.7.1 (???)
/System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfig\
uration
0x90d40000 - 0x90d40fff com.apple.Carbon 10.3 (???)
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x90d60000 - 0x90d6bfff com.apple.opengl 1.3.3
/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x910b0000 - 0x910fffff com.apple.bom 1.2.4 (63)
/System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
0x912a0000 - 0x912bdfff com.apple.audio.SoundManager 3.8
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.fr\
amework/Versions/A/CarbonSound
0x912e0000 - 0x912f7fff com.apple.LangAnalysis 1.5.4
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/L\
angAnalysis.framework/Versions/A/LangAnalysis
0x91303000 - 0x913c1fff ColorSync
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/C\
olorSync.framework/Versions/A/ColorSync
0x917e0000 - 0x917f0fff com.apple.speech.recognition.framework 3.3
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognit\
ion.framework/Versions/A/SpeechRecognition
0x91810000 - 0x9182afff com.apple.openscripting 1.2.1 (???)
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.\
framework/Versions/A/OpenScripting
0x91850000 - 0x91860fff com.apple.ImageCapture 2.1.0
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.f\
ramework/Versions/A/ImageCapture
0x91890000 - 0x9189cfff com.apple.help 1.0.1
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework\
/Versions/A/Help
0x918c0000 - 0x918cdfff com.apple.CommonPanels 1.2.1 (1.0)
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.f\
ramework/Versions/A/CommonPanels
0x918f0000 - 0x9193efff com.apple.print.framework.Print 3.3
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewor\
k/Versions/A/Print
0x91990000 - 0x9199bfff com.apple.securityhi 1.2 (90)
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fra\
mework/Versions/A/SecurityHI
0x919c0000 - 0x91a33fff com.apple.NavigationServices 3.3.1
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServ\
ices.framework/Versions/A/NavigationServices
0x91ab0000 - 0x91ac4fff libCGATS.A.dylib
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/C\
oreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x91ae0000 - 0x91aebfff libCSync.A.dylib
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/C\
oreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x91b10000 - 0x91b2afff libPDFRIP.A.dylib
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/C\
oreGraphics.framework/Versions/A/Resources/libPDFRIP.A.dylib
0x91b50000 - 0x91b5ffff libPSRIP.A.dylib
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/C\
oreGraphics.framework/Versions/A/Resources/libPSRIP.A.dylib
0x91b80000 - 0x91b93fff libRIP.A.dylib
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/C\
oreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x91bb0000 - 0x91d45fff com.apple.QuickTime 6.5.1
/System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
0x92070000 - 0x92096fff com.apple.FindByContent 1.4 (1.2)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/F\
indByContent.framework/Versions/A/FindByContent
0x920c0000 - 0x922a7fff com.apple.security 2.3 (176)
/System/Library/Frameworks/Security.framework/Versions/A/Security
0x92430000 - 0x92468fff com.apple.LaunchServices 10.3.4 (98.2)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/L\
aunchServices.framework/Versions/A/LaunchServices
0x92740000 - 0x92777fff com.apple.CFNetwork 1.2.1 (7)
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwor\
k.framework/Versions/A/CFNetwork
0x927d0000 - 0x92b54fff com.apple.HIToolbox 1.3.3 (???)
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fram\
ework/Versions/A/HIToolbox
0x92cca000 - 0x92d02fff com.apple.AE 1.3.2
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/A\
E.framework/Versions/A/AE
0x92d30000 - 0x92d80fff com.apple.HIServices 1.4.1 (0.0.1d1)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/H\
IServices.framework/Versions/A/HIServices
0x935d0000 - 0x938a8fff com.apple.CoreGraphics 1.203.20 (???)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/C\
oreGraphics.framework/Versions/A/CoreGraphics
0x939a0000 - 0x939b4fff libcups.2.dylib  /usr/lib/libcups.2.dylib
0x939d0000 - 0x939d4fff libmathCommon.A.dylib
/usr/lib/system/libmathCommon.A.dylib
0x94060000 - 0x94078fff com.apple.WebServices 1.1.1 (1.1.0)
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServi\
cesCore.framework/Versions/A/WebServicesCore
0x945b0000 - 0x945b9fff libz.1.dylib  /usr/lib/libz.1.dylib
0x94610000 - 0x9462afff libresolv.9.dylib  /usr/lib/libresolv.9.dylib
0x94650000 - 0x946affff com.apple.SearchKit 1.0.2
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKi\
t.framework/Versions/A/SearchKit
0x94b20000 - 0x94badfff com.apple.ink.framework 55.8
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/\
Versions/A/Ink
0x94c1a000 - 0x94c2dfff com.apple.speech.synthesis.framework 3.2
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/S\
peechSynthesis.framework/Versions/A/SpeechSynthesis
0x94d15000 - 0x94da8fff com.apple.print.framework.PrintCore 3.3
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/P\
rintCore.framework/Versions/A/PrintCore
0x9540b000 - 0x95474fff com.apple.htmlrendering 1.1.2
/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.\
framework/Versions/A/HTMLRendering
0x968d0000 - 0x969b2fff libicucore.A.dylib
/usr/lib/libicucore.A.dylib
0x96a20000 - 0x96ae2fff libcrypto.0.9.7.dylib
/usr/lib/libcrypto.0.9.7.dylib
0x96b40000 - 0x96b6efff libssl.0.9.7.dylib
/usr/lib/libssl.0.9.7.dylib
0x96bf0000 - 0x96c7ffff ATS
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/A\
TS.framework/Versions/A/ATS
0x97510000 - 0x97518fff libbsm.dylib  /usr/lib/libbsm.dylib
0x9751c000 - 0x975d5fff com.apple.QD 3.4.64 (???)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/Q\
D.framework/Versions/A/QD


________________________________________________________________________
Keith Wiley                                kwiley@...
http://www.unm.edu/~keithw                 http://www.mp3.com/KeithWiley

"Yet mark his perfect self-contentment, and hence learn his lesson,
that to be self-contented is to be vile and ignorant, and that to
aspire is better than to be blindly and impotently happy."
                                            --  Edwin A. Abbott, Flatland
________________________________________________________________________

Hi Giles!  Good to hear from you again.

At 10:49 AM +0000 8/3/04, gray39ghost wrote:

>My latest project has been to take up the Elite-remaking mantle and
>create Oolite, a fully fledged version of the original game.
>
>Oolite's website is at:
>
>http://oolite.aegidian.org/

Looks cool!  Thanks for making it available.

>I saw the work that had been done on RBElite in various places, do I
>take it that project is, if not dead, then pining for the fjords?

Yes, it died of apathy... please feel free to pick it up and run with
it.  I still think it has a lot of potential.

>What's the ETA on a new version of Meshwork?

I don't announce ETAs, so that I never miss them.  :)

Best,
- Joe

--
,------------------------------------------------------------------.
|    Joseph J. Strout         Check out the Mac Web Directory:     |
|    joe@...           http://www.macwebdir.com/            |
`------------------------------------------------------------------'

Hi Joe,

Been a long time since I last has anything to say about Meshwork, but that's not
to say I
haven't been using and enjoying it since 1999!

My latest project has been to take up the Elite-remaking mantle and create
Oolite, a fully
fledged version of the original game.

Oolite's website is at:

http://oolite.aegidian.org/

Naturally, I used Meshwork to make all the models (which are allavailable in the
source
code).

I saw the work that had been done on RBElite in various places, do I take it
that project is,
if not dead, then pining for the fjords?

What's the ETA on a new version of Meshwork?

Hope all's well!

-- Giles Williams

(who previously used Meshwork & RealBASIC to create MeQanno - the only quake
model
editor ever released for the Mac).

Likewise, I am also friends with him, though I am not a programmer.  I
haven't heard from him recently either.  I think meshwork needs a
plugin ability.  That way, you could and new import/export tools, and
just new tools period.  It would be nice if it could import/export
multiple flavors of DFX and 3DS.  And I think it should have more
color/texture labels for game development purposes.  Some games refer
to a model as separate models with names for the different parts, and
the texture naming could be used for that if there were more than 8
color/texture choices.
On Saturday, July 31, 2004, at 09:05 AM, Keith Wiley wrote:

> Well, yeah, I do owe him that.  We're friends actually.  I kinda
> figured, since the file format is ASCII and he explicitly explains it
> in
> full detail in the docs of the program, that he is practically inviting
> people to hack the file format for themselves, but I'll discuss it
> with him.
>
> BTW, is he around?  I've sent him a couple emails recently with no
> reply.  Perhaps he's on vacation or something.
>
> Tyranitar wrote:
>
>> I do agree, using the standard mapping in Meshwork is a bit tough.  I
>> never use it because it was too cumbersome, and the type of models I
>> do
>> not require it.  Also, before you write a program that directly writes
>> to Meshwork files, be certain you contact Joe first and clear any
>> details with him.
>> On Thursday, July 29, 2004, at 11:54 PM, Keith wrote:
>>
>>
>>
>>> Hmmm, I didn't even know there were any response.  Yahoo is not
>>> sending me any posts for this group.  I have my settings for
>>> individual email and I'm gettings posts for other yahoo groups.
>>> Sheez!
>>>
>>> Anyway.  Jeff, thanks for the response, and to the other guy (can't
>>> remember your name and can't see it since I'm using yahoo to write
>>> the
>>> message right now) I do mean UV mapping.  I suppose texture mapping
>>> is
>>> similar, but I am trying to assign uv coordinates to geometry
>>> vertices.  Therefore I am trying to map uv coordinates to vertices.
>>> Therefore, uv mapping.  I'm pretty sure that's the right term.
>>>
>>> So, thanks, I'll have to think about it.  Bottom line is I'll
>>> probably
>>> end up writing a little uv editing program that will let me easily
>>> edit uv coordinates, probably reading and writing the Meshwork file
>>> format directly so I can simply use it to properly map uv on an
>>> otherwise Meshwork file.
>>>
>>> Thanks.
>>>
>>>
>>>
>>> Meshwork Home: http://codenautics.com/meshwork/
>>> Mailing List:  http://www.egroups.com/group/meshwork/
>>>
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>> Meshwork Home: http://codenautics.com/meshwork/
>> Mailing List:  http://www.egroups.com/group/meshwork/
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>>
>>
>
> --
>
> _______________________________________________________________________
> _
> Keith Wiley                                kwiley@...
> http://www.unm.edu/~keithw
> http://www.mp3.com/KeithWiley
>
> "Yet mark his perfect self-contentment, and hence learn his lesson,
> that to be self-contented is to be vile and ignorant, and that to
> aspire is better than to be blindly and impotently happy."
>                                            --  Edwin A. Abbott,
> Flatland
> _______________________________________________________________________
> _
>
>
>
>
> Meshwork Home: http://codenautics.com/meshwork/
> Mailing List:  http://www.egroups.com/group/meshwork/
>
> Yahoo! Groups Links
>
>
>
>
>

Well, yeah, I do owe him that.  We're friends actually.  I kinda
figured, since the file format is ASCII and he explicitly explains it in
full detail in the docs of the program, that he is practically inviting
people to hack the file format for themselves, but I'll discuss it with him.

BTW, is he around?  I've sent him a couple emails recently with no
reply.  Perhaps he's on vacation or something.

Tyranitar wrote:

>I do agree, using the standard mapping in Meshwork is a bit tough.  I
>never use it because it was too cumbersome, and the type of models I do
>not require it.  Also, before you write a program that directly writes
>to Meshwork files, be certain you contact Joe first and clear any
>details with him.
>On Thursday, July 29, 2004, at 11:54 PM, Keith wrote:
>
>
>
>>Hmmm, I didn't even know there were any response.  Yahoo is not
>>sending me any posts for this group.  I have my settings for
>>individual email and I'm gettings posts for other yahoo groups.  Sheez!
>>
>>Anyway.  Jeff, thanks for the response, and to the other guy (can't
>>remember your name and can't see it since I'm using yahoo to write the
>>message right now) I do mean UV mapping.  I suppose texture mapping is
>>similar, but I am trying to assign uv coordinates to geometry
>>vertices.  Therefore I am trying to map uv coordinates to vertices.
>>Therefore, uv mapping.  I'm pretty sure that's the right term.
>>
>>So, thanks, I'll have to think about it.  Bottom line is I'll probably
>>end up writing a little uv editing program that will let me easily
>>edit uv coordinates, probably reading and writing the Meshwork file
>>format directly so I can simply use it to properly map uv on an
>>otherwise Meshwork file.
>>
>>Thanks.
>>
>>
>>
>>Meshwork Home: http://codenautics.com/meshwork/
>>Mailing List:  http://www.egroups.com/group/meshwork/
>>
>>Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>Meshwork Home: http://codenautics.com/meshwork/
>Mailing List:  http://www.egroups.com/group/meshwork/
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>

--

________________________________________________________________________
Keith Wiley                                kwiley@...
http://www.unm.edu/~keithw                 http://www.mp3.com/KeithWiley

"Yet mark his perfect self-contentment, and hence learn his lesson,
that to be self-contented is to be vile and ignorant, and that to
aspire is better than to be blindly and impotently happy."
                                            --  Edwin A. Abbott, Flatland
________________________________________________________________________

I do agree, using the standard mapping in Meshwork is a bit tough.  I
never use it because it was too cumbersome, and the type of models I do
not require it.  Also, before you write a program that directly writes
to Meshwork files, be certain you contact Joe first and clear any
details with him.
On Thursday, July 29, 2004, at 11:54 PM, Keith wrote:

> Hmmm, I didn't even know there were any response.  Yahoo is not
> sending me any posts for this group.  I have my settings for
> individual email and I'm gettings posts for other yahoo groups.  Sheez!
>
> Anyway.  Jeff, thanks for the response, and to the other guy (can't
> remember your name and can't see it since I'm using yahoo to write the
> message right now) I do mean UV mapping.  I suppose texture mapping is
> similar, but I am trying to assign uv coordinates to geometry
> vertices.  Therefore I am trying to map uv coordinates to vertices.
> Therefore, uv mapping.  I'm pretty sure that's the right term.
>
> So, thanks, I'll have to think about it.  Bottom line is I'll probably
> end up writing a little uv editing program that will let me easily
> edit uv coordinates, probably reading and writing the Meshwork file
> format directly so I can simply use it to properly map uv on an
> otherwise Meshwork file.
>
> Thanks.
>
>
>
> Meshwork Home: http://codenautics.com/meshwork/
> Mailing List:  http://www.egroups.com/group/meshwork/
>
> Yahoo! Groups Links
>
>
>
>
>

Hmmm, I didn't even know there were any response.  Yahoo is not
sending me any posts for this group.  I have my settings for
individual email and I'm gettings posts for other yahoo groups.  Sheez!

Anyway.  Jeff, thanks for the response, and to the other guy (can't
remember your name and can't see it since I'm using yahoo to write the
message right now) I do mean UV mapping.  I suppose texture mapping is
similar, but I am trying to assign uv coordinates to geometry
vertices.  Therefore I am trying to map uv coordinates to vertices.
Therefore, uv mapping.  I'm pretty sure that's the right term.

So, thanks, I'll have to think about it.  Bottom line is I'll probably
end up writing a little uv editing program that will let me easily
edit uv coordinates, probably reading and writing the Meshwork file
format directly so I can simply use it to properly map uv on an
otherwise Meshwork file.

Thanks.

What do you mean by uv mapping?  Do you mean texture mapping, or the
alpha mask.  I have never used texture mapping before, but uv mapping
sounds like a pc term.  If you mean texture mapping, say texture
mapping or tex mapping.
On Tuesday, July 27, 2004, at 03:21 PM, Keith Wiley wrote:

> Joe, can you justify Meshwork's uv behavior for me.  I don't understand
> why the program intentionally reverts uv coordinates in the first
> place.
> uv coordinates are on a vertex by vertex basis.  Aside from asthetic
> issues, they are completely independent of all over uv coordinates.
> You
> can theoretically make any vertex's uv coordinate anything you want,
> without regard for any other uv coordinates.
>
> Therefore, if I select a subset of vertices and create a uv mapping to
> those vertices, then I don't see any reason why those uv mappings
> should
> ever be automatically changed just because a completely different
> subset
> of vertices is given a different mapping on the same texture.
>
> I think Meshwork would be a lot easier to use if it didn't have this
> feature, but the funny thing is that it must be an intentional feature,
> which really confuses me.  I can't for the life of me imagine why the
> program does this in the first place.  Is there ever a situation where
> this is beneficial?
>
> Is there a good reason I'm not aware of?  I think the only way I'm
> going
> to be able to get the uv mapping I want is to write my own uv mapping
> software, but Meshwork has all the infrastructure in place.  It would
> be a
> lot easier to just turn that feature off,recompile, and release a new
> version for me...or anyone else who would find it useful.
>
> In short, all I need the program to do, is apply any given mapping
> command
> to only the visible vertices and simply ignore the hidden vertices --
> just
> don't change their present uv values, just leave them as they are.  How
> hard is that, right?  This must be possible, right?
>
> Final thought, perhaps I can hack the behavior I want by using a backup
> copy of the Meshwork file, and copying over the uv coordinates that I
> didn't want mangled after the new mapping is assigned, but again, why
> should such tedium be necessary to circumvent an intentional feature?
>
> Thanks for any explanation.  I'm confused at the moment.
>
> Cheers!
>
> _______________________________________________________________________
> _
> Keith Wiley                                kwiley@...
> http://www.unm.edu/~keithw
> http://www.mp3.com/KeithWiley
>
> "Yet mark his perfect self-contentment, and hence learn his lesson,
> that to be self-contented is to be vile and ignorant, and that to
> aspire is better than to be blindly and impotently happy."
>                                            --  Edwin A. Abbott,
> Flatland
> _______________________________________________________________________
> _
>
>
> Meshwork Home: http://codenautics.com/meshwork/
> Mailing List:  http://www.egroups.com/group/meshwork/
>
> Yahoo! Groups Links
>
>
>
>
>

On Jul 27, 2004, at 3:09 PM, Keith Wiley wrote:
> I don't understand the circumstances under which Meshwork reverts all
> the
> UV coordinates.  I select a portion of the model, hide the rest,
> assign a
> mapping, show all, select a new portion, hide the rest, assign a
> mapping
> to that, and for some reason Meshwork has altered the previous UV
> coordinates even though they aren't related to the new coordinates.  In
> some cases I have disconnected portions of a model using the same
> texture
> and I thought that at least in that case it would work, but it doesn't.
> It reverts all the UV coordinates for the entire model everything I
> assign
> a mapping to some subset of the vertices.
>
> Is there anything that can be done about this?

Unfortunately, not in the current incarnation of Meshwork. Perhaps the
next version will add this functionality.
If you describe what you want to tile, perhaps there's a workaround.
There are ways of getting that repeating-tile effect without dedicating
an entire material to it, although none are as easy selecting subsets
of vertices.

==
Jeff Quan
jquan@...

Joe, can you justify Meshwork's uv behavior for me.  I don't understand
why the program intentionally reverts uv coordinates in the first place.
uv coordinates are on a vertex by vertex basis.  Aside from asthetic
issues, they are completely independent of all over uv coordinates.  You
can theoretically make any vertex's uv coordinate anything you want,
without regard for any other uv coordinates.

Therefore, if I select a subset of vertices and create a uv mapping to
those vertices, then I don't see any reason why those uv mappings should
ever be automatically changed just because a completely different subset
of vertices is given a different mapping on the same texture.

I think Meshwork would be a lot easier to use if it didn't have this
feature, but the funny thing is that it must be an intentional feature,
which really confuses me.  I can't for the life of me imagine why the
program does this in the first place.  Is there ever a situation where
this is beneficial?

Is there a good reason I'm not aware of?  I think the only way I'm going
to be able to get the uv mapping I want is to write my own uv mapping
software, but Meshwork has all the infrastructure in place.  It would be a
lot easier to just turn that feature off,recompile, and release a new
version for me...or anyone else who would find it useful.

In short, all I need the program to do, is apply any given mapping command
to only the visible vertices and simply ignore the hidden vertices -- just
don't change their present uv values, just leave them as they are.  How
hard is that, right?  This must be possible, right?

Final thought, perhaps I can hack the behavior I want by using a backup
copy of the Meshwork file, and copying over the uv coordinates that I
didn't want mangled after the new mapping is assigned, but again, why
should such tedium be necessary to circumvent an intentional feature?

Thanks for any explanation.  I'm confused at the moment.

Cheers!

________________________________________________________________________
Keith Wiley                                kwiley@...
http://www.unm.edu/~keithw                 http://www.mp3.com/KeithWiley

"Yet mark his perfect self-contentment, and hence learn his lesson,
that to be self-contented is to be vile and ignorant, and that to
aspire is better than to be blindly and impotently happy."
                                            --  Edwin A. Abbott, Flatland
________________________________________________________________________

I have seen Jeff's tutorials, but for now I don't want to unwrap
everything into a square.  I actually want to reuse large portions of the
map in a tiling fashion to get high resolution on the surface of the
model.

I don't understand the circumstances under which Meshwork reverts all the
UV coordinates.  I select a portion of the model, hide the rest, assign a
mapping, show all, select a new portion, hide the rest, assign a mapping
to that, and for some reason Meshwork has altered the previous UV
coordinates even though they aren't related to the new coordinates.  In
some cases I have disconnected portions of a model using the same texture
and I thought that at least in that case it would work, but it doesn't.
It reverts all the UV coordinates for the entire model everything I assign
a mapping to some subset of the vertices.

Is there anything that can be done about this?

________________________________________________________________________
Keith Wiley                                kwiley@...
http://www.unm.edu/~keithw                 http://www.mp3.com/KeithWiley

"Yet mark his perfect self-contentment, and hence learn his lesson,
that to be self-contented is to be vile and ignorant, and that to
aspire is better than to be blindly and impotently happy."
                                            --  Edwin A. Abbott, Flatland
________________________________________________________________________

Joe, in your next version, do you think it could be possible to add a plugin
capability, so that adding new exporters would be simpler and more integrated. 
Then
people could write custom import/export programs, and they could be integrated
into meshwork.  Plugins would be a great way to keep meshwork simple, while
adding
functionality.

--- In meshwork@yahoogroups.com, "Joseph J. Strout" <joe@s...> wrote:
> At 2:10 AM +0000 1/17/04, Jess wrote:
>
> >Don't want to bug anyone, but I've got a few projects I can't work
> >on until I have a mac program that lets me make skn files for
> >TheSims. I've heard that the export freature is in the works and I'd
> >just like to know how far it's gotten, that sort of thing. ;-)
>
> Unfortunately, I have to report that this feature is on hold.  I'm in
> the middle of a complete rewrite of Meshwork, to fix some things that
> I have long wanted to fix.  But new importers & exporters will have
> to wait for that to be done first.
>
> In the meantime, your best bet is probably to find someone clever to
> make a translator (something that reads Meshwork files and spits out
> SKN).  Unfortunately SKN is a very difficult format to work with, so
> this is not a trivial job.
>
> Best,
> - Joe
>
> --
>
> ,------------------------------------------------------------------.
> |    Joseph J. Strout         Codenautics: quality Mac software    |
> |    joe@s...           http://codenautics.com/              |
> `------------------------------------------------------------------'

At 1:07 PM -0400 5/1/04, Daniel Lurie wrote:

>If I assign a u,v greater than 1, will it make the texture repeat?

That's up to the engine doing the rendering, but with every rendering
engine I've ever seen, yes, it will.

Cheers,
- Joe

--
,------------------------------------------------------------------.
|    Joseph J. Strout         Check out the Mac Web Directory:     |
|    joe@...           http://www.macwebdir.com/            |
`------------------------------------------------------------------'

On May 1, 2004, at 10:07 AM, Daniel Lurie wrote:
> If I assign a u,v greater than 1, will it make the texture repeat?
>

Yep.


Jeff Quan
jquan@...

If I assign a u,v greater than 1, will it make the texture repeat?

============
Daniel R. Lurie
============

On Apr 17, 2004, at 12:34 PM, Phil Atkin wrote:

> So - could somebody let me know what fourcc to set as the file types
> (I can do this in
> DefaultFolder) so that meshwork will open 3DS files?
>
The easiest way to find out what file type Meshwork expects a 3DS file
to be is to export a model as 3DS and examine its file type. Meshwork
sets them as follows:

Type: 3DSM
Creator: ????

> And can I also add my voice to the 'its better to let it try to open
> them' school of
> thought for the next revision.

At the very least, Meshwork should attempt to import any file that has
a .3DS extension regardless of file type. That way, we can at least
correct it ourselves from the Finder instead of monkeying with the
metadata. If it really wasn't a 3DS file and Meshwork's import fails,
that's fine with me.

Bob

I just installed DefaultFolder as suggested, couldn't via any combination of
ctrl option
or 'apple' get the 3DS files to appear anything other than greyed out. I also
just got
the 3 droplets discussed earlier but they are classic-only and I have no
interest in
running classic anymore.

So - could somebody let me know what fourcc to set as the file types (I can do
this in
DefaultFolder) so that meshwork will open 3DS files?

And can I also add my voice to the 'its better to let it try to open them'
school of
thought for the next revision.

Phil

Jeffrey,

I have in my collection three applescript droplets that may be of use
to you. I can't right now remember where I found them or I would simply
direct you there. They were specifically designed to fix files that
were sent from a PC to a Mac or downloaded from the internet. Together
they are less than 100 kb. I would be glad to send them to you if you
are interested.

One droplet fixes 3ds files, the second .obj files and the third does
.dxf files. Let me know....

HTH
Regards,
Don

On Mar 24, 2004, at 4:59 PM, Jeffrey Greenland wrote:

> The files in question were from a zip file off a Windows PC.
> Safari seems to have no useful file helper preferences...

> All files on the Mac have a file type; but if you haven't set up your
> browser/PC-exchange settings properly, it may not have the *right*
> file type.  Just fix them (or fix your settings so you don't have to
> keep doing it).

The files in question were from a zip file off a Windows PC.
Safari seems to have no useful file helper preferences...

> Because Meshwork would get very confused, and perhaps even crash, if
> you tried to open a picture or database or MP3 file as a 3DS.  File
> type filters are a good thing; they're there to make your life
> easier.  If you're getting files that are improperly typed, you
> should fix that, not rail against apps which look for the correct
> type.

That is understandable... But consider for a moment which is more annoying:
A. an app that opens a file the user tells it to but is INCORRECT and crashes
or
B. an app that should be able to open a CORRECT file but does not

Also, I don't think there is a Mac version of 3DSmax and I don't know how the
average user
would be expected to know what four-character file type it should be as most
don't even
know they exist.  My point is that these files can come from dozens of different
3D
applications on different operating systems and Meshwork should be mindful of
this.
It would be nice, instead of downright refusing to open a file that the user
knows it is fully
capible of doing, if Meshwork displayed a caution dialog if the file-type or
suffix is not
what it should be... maybe even offer to correct it.  Many applications do this.

I'm not trying to "Rail" on this awesome application, I'm meerely telling you
that when it
comes in omporting files, it is almost as obnoxious as I am.  Stop being so
defensive.  This
is the best shareware application I ever purchaced and I use it on a daily
basis...
Hell, I'd buy it again if Undo came back and it was not so picky about file
types.

Who else would?

At 8:30 PM +0000 3/24/04, Jeffrey Greenland wrote:

>It's the same thing for DXF import.  It oddly enough, accepts Adobe
>Illustrator files and
>nothing else...  so I end up having to copy an illustrator file and
>then use BBEdit to carve
>out it's contents and paste in the DXF data...

Er... a much better solution would be to use a file typer utility
(such as FileTyper) to just fix the broken DXF files.  Then, fix your
browser settings so that when you download such files in the future,
they get the right type assigned.

Or if you really want, you can get a system extension such as
DefaultFolder that allows you to hold a modifier key down in any file
dialog, and select any file even if it doesn't have the right type.

Cheers,
- Joe

--
,------------------------------------------------------------------.
|    Joseph J. Strout         Check out the Mac Web Directory:     |
|    joe@...           http://www.macwebdir.com/            |
`------------------------------------------------------------------'

At 4:48 AM +0000 3/24/04, Jeffrey Greenland wrote:

>What I find extremely frustrating is the inability to import 3DS files...
>I know its in the menu... it's might even work.
>But how will I ever know if it does not let me select the file?
>There all grayed out!

That just means that your 3DS files have the wrong file type.  That
often happens when you download them from the net.

>....if it's a 3DS file off the internet/PC, why would it have a
>creator code/file type?

All files on the Mac have a file type; but if you haven't set up your
browser/PC-exchange settings properly, it may not have the *right*
file type.  Just fix them (or fix your settings so you don't have to
keep doing it).

>How come I can't open it??

Because it has the wrong file type.

>Why can't the import functions use all/???? file types?

Because Meshwork would get very confused, and perhaps even crash, if
you tried to open a picture or database or MP3 file as a 3DS.  File
type filters are a good thing; they're there to make your life
easier.  If you're getting files that are improperly typed, you
should fix that, not rail against apps which look for the correct
type.

Cheers,
- Joe

--

,------------------------------------------------------------------.
|    Joseph J. Strout         Codenautics: quality Mac software    |
|    joe@...           http://codenautics.com/              |
`------------------------------------------------------------------'

It's the same thing for DXF import.  It oddly enough, accepts Adobe Illustrator
files and
nothing else...  so I end up having to copy an illustrator file and then use
BBEdit to carve
out it's contents and paste in the DXF data...
--- In meshwork@yahoogroups.com, "Jeffrey Greenland" <darkoceangames@y...>
wrote:
> What I find extremely frustrating is the inability to import 3DS files...
> I know its in the menu... it's might even work.
> But how will I ever know if it does not let me select the file?  There all
grayed out!
> ....if it's a 3DS file off the internet/PC, why would it have a creator
code/file type?
>
> How come I can't open it??
> Why can't the import functions use all/???? file types?  Unless I ResEdit them
all before
> importing.  They don't always match up. >_<
>
> ..or am I missing something?

What I find extremely frustrating is the inability to import 3DS files...
I know its in the menu... it's might even work.
But how will I ever know if it does not let me select the file?  There all
grayed out!
....if it's a 3DS file off the internet/PC, why would it have a creator
code/file type?

How come I can't open it??
Why can't the import functions use all/???? file types?  Unless I ResEdit them
all before
importing.  They don't always match up. >_<

..or am I missing something?

Hi all,
I just came across an interesting app which does UV unwrapping. It's a
Windows app called Unwrap3D. You can find it here:
<http://www.unwrap3d.com/index.html>

Now it's not the program that caught my eye, but rather the tutorials
showing how it handles UV. This one in particular:
<http://www.geocities.com/jhocking15213/unwrap/tutorial_char.html>

If you read through the tutorial, you'll notice how it handles building
a single UV map by selecting groups of vertices and telling it to
unwrap via the standard planar/cylindrical/spherical projections, which
you can then translate however you want to fit within the material.

What's really appealing to me is that it takes the basic functionality
of Meshwork's materials and takes it a step further, allowing one to
combine multiple unwraps into one material by using projections similar
to Meshwork's material mapping. It looks like the app remembers each
selection selection group, allowing one to scale/move/rotate the whole
group at once. Imagine if Meshwork's texture window did that -- no need
for a fancy unfolding polytope algorithm, just use what Meshwork
already has!

I haven't read through the other tutorials, but this process seems to
be ideal for Meshwork. I thought I just throw this out there and see
what sticks.


==
Jeff Quan
jquan@...

On Jan 28, 2004, at 10:51 PM, Seth Willits wrote:

> On Jan 28, 2004, at 10:14 PM, Jeffrey Greenland wrote:
>
>> Five bucks says I have the best model ever. ^_^  I will donate it for
>> your twisted
>> experiments if you want to make a converter.
>
> lol. I was really wondering mostly for believability that it was a
> good idea to work on it, but I'll take you up on it if I do.

My point being that this is the kind of stuff used in Torque and done
with DTS:
http://www.garagegames.com/mg/snapshot/view.php?qid=681


Seth Willits
------------------------------------------------------------------------
---
President and Head Developer of Freak Software - http://www.freaksw.com
REALbasic Guru at ResExcellence - http://www.resexcellence.com/realbasic
Webmaster for REALbasic Game Central - http://www.freaksw.com/rbgames

"Few are those who see with their own eyes and feel with their own
hearts."
      -- Albert Einstein
------------------------------------------------------------------------
---