linus

Pragmatically spoken, yes. But a user friendly installer would/should support also cut-down version as it's included in latest au3-package.

Hi, I am currently working on a new release of the UDF au3irrlicht2. Its setup is adding calltips to SciTe - and it would be nice to have this also compatible with SciTe light. But seems any calltip definition in au3.api is ignored if it begins with an underscore (which are all UDF functions ...). Everything ok with full SciTe, and also ok with SciTe light included in AutoIt installer 3.3.6.1 - but unfortunately NOT ok with SciTe light included in latest AU3 installer 3.3.8.1. Wondering if this a known error; and if there is maybe a workaround so I can keep au3irrlicht2 compatible with latest au3 installer? Thanks for any advice!

Hi bogQ, Reason to include constants.au3 in every sub-include again was to allow usage of only some of the au3Irr2 sub-includes instead of everything (as done by the main include). But at top of constants.au3 there is an "#includeOnce", so in fact constants are only included one time when compiling. Not sure what you mean - original help files ARE included (see "freeBasic wrapper docs" in au3Irr2 help file)? Hm, better handling of 64 bit was one thing on my todo for final 2.05. Amongst other things ... Problem since months: completely no time for this (too much family, too much job, too much other things). Don't know if or when it will change ... So don't know what's best for au3Irr2 - Hope for better times ... Leave it completely to others (JRowe seems to be definetly out, but maybe smashly, or ...) ... Retire as some kind of release provider (if some other continue work on sources, especially providing some more help content) ... BTW: thanks to you and those other few actives for keeping this thread alive

Hi monoscout999, adding requireadmin would also mean no more chance to run examples as non-admin. Not a good idea. Admin rights are only needed one time to merge the help - so why not right-click and "run as admin"? Merging help files requires re-compiling of the original autoit help file. Nothing to explain in two lines, but if really interested you can dig yourself into it: all required files, scripts and some readme is on the project page.

Nah - found it also some mins ago. Spending help time for nuts ... Who cares

you are placing the camera inside the model. Try $CAMERA = _IrrAddCamera( [somethingGreaterThenModelSize],0,0, 0,0,0 ). Maybe worth to spend also a night (again) with e.g. example 004 to get some basic understanding of principle usage

With visible usage of it in mind I would say: yes, it's dead. Don't think an update would change anything about this: already 2.04 has a quiete complete feature list, lots of example code and some basic documentation. But feel free to bring it back to life with a cool small project, it may be the missing motivation for new dev activity around this UDF OK, to be serious: I wish I would have some time again to to some 3D programming for fun. If this will happen, it will be also a reason to polish the UDF. In the meantime: why not use what is already there?

Well at least I have to find myself a free weekend to complete the 2.05 (your previous work on dev version + basic IrrKlang support + extending help for it + of course building the package). Maybe with some good-old-times-sunday-morning-coffee-disturbing At least January, I promise. And when seeing some cool things done with this baby, I am sure it will motivate to have also a look on some deeper things (e.g. .dll stuff) BTW: Mine is not a game but a new sequencer - nothing better than doing a bad never finished track after a day of work ) @boqQ: nah - branch'ing was a joke - you know I prefer the team thing. And of course smashly has rights on the project - he did good things on help, examples and funcs (and gave me back some of those lost motivation). End of laudation

Hi smashly, still alive - and still too busy combined with same old thing we mailed about: not too much usage to see to feel motivation (again) to put those limited hours into it. Means CURRENTLY, not at all! @bogQ: Yep; MIT - theoretically possible to create a branch. Also possible to join in - lot's of things open

1) Start read following postings and finally 2) Sketchup creates texture dir together with mesh export - otherwise check export options.

Right if you have both a working BMW and a Beetle in your garage - wrong if both need a lot of work until getting you somewhere - and you'll have just two hands. Better to decide what car is the best and make it ready to ride

Very good idea! Would say Irrlicht/IrrlichtWrapper has a lot of pros, but just from a very little knowledge of 3impact. Screenshots and written feature list of 3impact are impressive, but not enough to really judge. So would be great if you do/start a serious comparison! At least not a question of vanity but of efficiency: if both would/could target identical needs it would be stupid to divide available man power, right? At least one suitable 3D engine is enough for au3, no matter what it's name is.

Nah, was just joking But educational sounds good - keep concept small, make it working, add some nice comments, and we'll have something more for the coming \demo dir of au3Irr2 ...?! 2) Damned. So I wasn't wrong (but wanted to be )

Thanks in return - always nice to see people using au3Irr2 (and still in anticipation to see something finished; but ok, all those started nextGen FPS should take some years to finish ) Well, maybe we can complete this 64bit-thing: 1) you have 64bit and when running the example scripts without any changes it crashes, right? 2) what happens if you add #AutoIt3Wrapper_UseX64=n to the top of au3Irrlicht2.au3, then run example script exactly same way as before - hopefully it works?