from the bigining

Welcome to the Avolites Personality Builder Forum.

Moderator: Moderators

totalworks4u
Posts: 47
Joined: 19 Feb 2010, 20:26

from the bigining

Postby totalworks4u » 06 Nov 2011, 23:37

Hello there. I need the steps from the beginning to make the vizual work on expert.
I created the D4 personalities 4 expert myself and they work very well.
So what is next ?
User avatar
john rogers
Posts: 97
Joined: 18 May 2010, 12:29
Location: London
Contact:

Postby john rogers » 07 Nov 2011, 10:52

This post has been moved to the personality builder forum.
Last edited by john rogers on 07 Nov 2011, 11:44, edited 1 time in total.
Used to work at Avo. Freelance now.
User avatar
niclights
The eManual
Posts: 4442
Joined: 24 Sep 2004, 01:06
Location: UK

Postby niclights » 07 Nov 2011, 11:44

This is probably too complex to cover in a forum.

However, to start with you can try the automatic creation from Personality Builder:

Open your .d4 file, click on each mode and enter a device name (max 11 chars) into the 'Classic Pearl Reference' field. There should be a different name for each mode.

Now go to Wheel Mapping/Classic Pearl and organise mapping to suit. Where things go is not important for Vis as long as each attribute is in on a different wheel slot. Any conflicts or unassigned attributes will show in red. Once assigned click on each one and set the attribute type in the properties section. This is important. Each must be unique. If there is nothing suitable available set to Uncategorized (who spelt that wrong?!)

Now go to File/Generate R20 Files... and when the prompt appears say yes to create Visualiser files.

Give each mode a filename (max 8 chars).

The resulting .r20 files should be placed in C:\program files\avolites\visualiser\personalities\

The resulting .vis files should be placed in C:\program files\avolites\visualiser\extensions\

For these to auto-patch you will need also need to save the .d4 file with the Classic Pearl References you entered and ensure this is in c:\program files\avolites\titan\fixturelibrary\

Restart the software and test.


There are some essential requirements for Vis files to work:

- The device name must be the same in both the .r20 file and the associated .vis file.
- Both of these files must have exactly the same filename (with the exception of the extension)
- The device name must be unique.

If these conditions are all met and the vis file still does not work then it is likely that there is either a problem with the .vis mapping and/or the attribute type in the .r20 files.

At this stage it is probably a case of opening these files in a text editor and having a look.

Who is online

Users browsing this forum: No registered users and 9 guests