Profile Editor Problem

The first and last ranges' home values have special rules applied -- they will be set to the min and max, respectively. You can add an extra range to work around this hard-coded rule, as you observed.

Your other question needs a bit more context. If you can post the showfile or a screenshot of the parameters you are using, we might be able to see what's happening. As for how to add a new mode section in the range editor, the mode column can be added by pressing "New Mode" on the far left of the screenshot above.

Thanks for the Home values advice. Noted.

The "App A Custom Fixture Profiles" under Virtual Parameters tells me to "Click Gobo Mode and set DMX to 0 (Which doesn't make sense to me as we need a FMX (Offset) for the parameter. But to the real question. I have fumbled and found how to put in a new mode.

But can't find how to put text into their blocks. See above. Now I may be thinking things are more complicated than they are. But if you look a a Intimidator profile below

Not only is there text but - Is there a "IF" thing going on here? It is as if something is saying if a button in the ML panel is pressed then look at these ranges. If so how/where does the button come from and any program made? Sorry for being obtuse but I can find very little information on this whole mode thing and not really sure of the process.

Check out the manual page here: https://www.etcconnect.com/webdocs/Controls/EosFamilyOnlineHelp/en-us/Default.htm#Patch/Modes.htm%3FTocPath%3DPatch%7CFixture%2520Editor%7CCreating%2520a%2520New%2520Fixture%7C_____2

Towards the bottom of that page is a tutorial on how to create the mode parameter using a simple gobo rotator as the example fixture. 

To your question more directly, the labels for mode conditions are obtained from the range labels for the mode parameter. This is an entirely separate parameter that is defined (often without a DMX address) and set up before applying it as a condition. If you look in the Intimidator profile, there will be a Color Wheel Mode parameter that has three ranges defined, which are then available as conditions. 

This is a tad complex, let us know if this makes sense. 

Check out the manual page here: https://www.etcconnect.com/webdocs/Controls/EosFamilyOnlineHelp/en-us/Default.htm#Patch/Modes.htm%3FTocPath%3DPatch%7CFixture%2520Editor%7CCreating%2520a%2520New%2520Fixture%7C_____2

Towards the bottom of that page is a tutorial on how to create the mode parameter using a simple gobo rotator as the example fixture. 

To your question more directly, the labels for mode conditions are obtained from the range labels for the mode parameter. This is an entirely separate parameter that is defined (often without a DMX address) and set up before applying it as a condition. If you look in the Intimidator profile, there will be a Color Wheel Mode parameter that has three ranges defined, which are then available as conditions. 

This is a tad complex, let us know if this makes sense. 

Oh wow! I knew there must be some 'stuff' out there. But my manual does not contain this wealth of info. I'm cutting and pasting your notes and that great link into a "Profile Modes For Double Dummies" doc to work through. Interesting evening comin up. Thank you for your help.

Followed the instructions and created the "Gobo Wheel Mode" and "gobo index/speed" parameters per the instructions.
Had a few "Ranges can't overlap" messages but ended up saving OK.
However, back in the editor I noticed that the grayed out "Gobo Wheel Mode" had a DMX of 1 ?
The example Intimidator profile showed a Gobo Select at position 7 and much lower down a Gobo wheel Mode at 12. It was grayed out too but the DMX field was empty? How do I get rid of my DMX in the Gobo wheel mode. I repeated all for a new profile but made sure both the gobo wheel parameters were images but this didn't get rid of the DMX value

Ah, yes I see. Mode parameters become read-only once you assign them as conditions to other parameters.

In this case, you'll want to set the DMX value to 0 (to make it virtual) before applying it to the Index/Speed parameter. It will go back to being editable once you remove it from the Index/Speed parameter as a condition. 

Aha. I was having a problem zeroing out that DMX for a while but got it in the end. Several times during the process I had that "Ranges can't overlap" message" but said OK. The final profile saved without problems. One question to tidy things up. See my picture:

My (virtual) wheel mode is at 2 and my Index/Speed at 3. Now, in the Intimidator they make things a lot tidier by stick their 'virtual' parameters at the bottom of the list. Is this purely due to the order the parameters were entered or can I now say, swap my 2 and 3?

You have done a great job Hans. I now feel confident to go on to make a number of profiles with these virtual parameters. Thank you.

I'm glad I could help and very glad to hear you're feeling comfortable with the feature!

To answer your question - the parameter order is based off of the order of creation, so it isn't possible to rearrange them. 

The Ranges cannot overlap message happens whenever there's an overlap in either the user or DMX ranges. Having an overlap means some values may be ambiguous. Eos will choose _some_ value, but it's considered profile that needs correcting. (Long-term, I would like to remove those popup advisories and display something more specific on screen about where the problem is.)

OK on the order of entry. I guess the guys who do a lot of this can plan the neat layout up front. And yep, a very close examination showed the overlap.