View Full Version : LightWave Mac v9.6 Hotfix and Cocoa Update - 5 May 2009

05-05-2009, 11:39 AM
Hello Mac peeps!

I just wanted to check in with you, and let you all know that we are working on a hotfix release for LightWave v9.6, and continuing our work on a Cocoa release. I would encourage you to submit bugs through the fogbugz system, and don't forget to include content. For those of you who need a refresher as to how to report bugs, check this link:


I know that many of you are looking for information regarding our release of Cocoa, and while I cannot yet give you a date, I can tell you that it will still be another month or two. As soon as we can, we will get it into testing for you.

05-05-2009, 11:58 AM

05-05-2009, 12:00 PM
Sounds great Jay! :thumbsup:
Bring it on! :dance:

05-05-2009, 01:27 PM
Super - makes me feel all warm and fuzzy inside.

05-05-2009, 01:36 PM
Thanks very much Jay

Darth Mole
05-05-2009, 04:07 PM
Jay is the new Chilton

05-05-2009, 04:16 PM
And the new black :D

05-05-2009, 05:43 PM
Jay - that is great news!

I have a question. Can you tell me what language/compiler/platform used to develop LW? I used to program heavily in c & c++, and in assembly language back even further.

It might be possible they are overlooking some tools that would make it easier to locate what I guess are memory allocation bugs.

I've got a decent amount of time/$$ invested in LW, and I'd like to see Newtek bring out as bug free a version as possible, as that way everybody wins - so I'd gladly do a bit of research.


05-05-2009, 05:47 PM
LightWave v9.6 is written in C. LightWave CORE is written in C++.

05-05-2009, 05:56 PM
Jay - which compiler? Do you use an kind of 3rd party bounds checking software?

What this kind of software can do is add code to a debug build that checks to see if any memory issues crop up. Slows things down a bit, but with today's computers so fast ...

When I saw several crashes when on 'Clear Scene' - this is what came to mind - and what would easily detect and locate the problem code.

You just use another 3rd party to to automatically run a test suite using the debug version - and have it run overnight. The test suite would run thru all of the commands and operations - so that if you fix one bug, you find out if it broke another piece of code.

If you set up a number of automatic tests like this, it really saves time - and catches more bugs.

05-06-2009, 09:11 AM
gcc under xcode i beleive. (9.6 anyway)

05-06-2009, 10:06 AM
The tools for bounds checking/sanity checking may be more available on the PC platform - and hopefully many of the errors will be in the common code set shared between platforms.

This could be used for the PC platform:

for xcode, they do have automation tools for running test suites:

and I'd guess that if the developers got on the developer discussion groups and asked, they could find some bounds checking tools to catch memory errors that are 100% going to happen when coding in C.

Been so long since I coded in C, but I believe it doesn't even have try/catch or constructors/destructors - which make it a lot harder to code.

paul summers
05-06-2009, 10:31 AM
Thanks Jay

about time:thumbsup:

05-06-2009, 12:44 PM
64-bit is an exciting feature to look forward to! Thanks Jay

05-07-2009, 07:21 AM
Thanks for the update, Jay! :D

05-11-2009, 11:12 AM
thanks for the update Jay . . .