No, all paths are already added as add_folder.
Its a strange one, and being A7 may well not be fixed?
Will check if same in A8 later on.

Just wanted to drop by and say i love the new possibility to call lite-c scripts from C#. I was able to get Shade-C working in C# in no time.

Thanks!

great to hear that ^^

This website's really the best.

a new version was uploaded (for Acknex 7.85.4 AND Acknex 8.10)
the update of the wrapper includes:

- engine_getvar, wrong return type, wrong type for type parameter - fixed
- engine_getvarinfo, wrong return type, wrong type for type parameter - fixed
- engine_debugposition, wrong return type, wrong type for type parameter - fixed
- EventOnBreakPoint, wrong type of the line argument - fixed

here's the link:

AcknexWrapper_2_2_4_FOR_8_10_AND_7_85_4.zip

+ an example to show how to use some debug functions has been added to the examples page

Hi,
Thank you for the work you put into this

I have a small problem.
I am using different classes.
I am creating the instances of this classes in my Scheduled main method.
Now I want to run a Scheduled method within this class. It is a classmember function with a wait in it.
The function is called by the constructor of my new class.
But until now the funtiction will not run, even it is called from the constuctor,


Perhaps I don't understand the concept of the Scheduler.

the method StartGamepad seams to be correct !
the problem is that the StartGamepad method is an IEnumerable, thus you can't directly call it !
to add an IEnumerable to the Scheduler, you have to add it, using Scheduler.AddEventVoid(...)

in your case instead of trying to call it like :

call it like this :


Scheduler.AddEventVoid method also immediately returns, after it has run the method for one time and then attached it to the scheduler !

Thank you. It works fine

It is great to work with the engine AND classes

a new version was uploaded (for Acknex 7.85.4 AND Acknex 8.10)
the update of the wrapper includes:

- ScheduleMethod.executeEventVoid and ScheduleMethod.executeEventObject added - they allow to execute functions not "beside" but "inside" the function they are called
- EVENT_BLOCK, EVENT_ENTITY, EVENT_FRICTION, EVENT_PUSH, EVENT_IMPACT, EVENT_SHOOT, EVENT_SONAR, EVENT_SCAN, EVENT_DETECT, EVENT_TRIGGER, EVENT_TOUCH, EVENT_RELEASE, EVENT_CLICK, EVENT_RIGHTCLICK, EVENT_RECEIVE, EVENT_DISCONNECT and EVENT_FRAME were wrongfully implemented as ENTITY flags - removed from ENTITY
- Scheduler.StartScheduler(null) didn't work - fixed

The new ScheduleMethod.executeEventVoid and ScheduleMethod.executeEventObject feature in comparision to the Scheduler.AddEventVoid feature


here's the link:

AcknexWrapper_2_2_5_FOR_8_10_AND_7_85_4.zip

+ an example which shows the two types of method calling in the scheduler

a new version was uploaded (for Acknex 7.85.4 AND Acknex 8.10)
the update of the wrapper includes:

- calling ScheduleMethod.executeEventVoid and ScheduleMethod.executeEventObject as the first “yield” command in a method added by Scheduler.AddEventVoid resulted in wrong scheduler behaviour – fixed

here's the link:

AcknexWrapper_2_2_6_FOR_8_10_AND_7_85_4.zip