The issue with the constantly recreating framebuffer is known and I thought it's fixed in 4.2.5. The "no uniform pass in shader" is not an error. Also the warnings in the log are okay. So I can only postpone this to the new gui which will fix a lot of problems :D

Update: no way....Unfortunately now even old updates do not work, the CPU remains at 50%. To get the CPU to 25% in Vis Editor I had to install the drivers released on 2014... and I'm not at all happy about this. I want my graphic card updated. I wonder if developers can understand the reason for this problem. When I first installed the Nvidia driver updates, Visionaire would crash when opening. Looking in the Event Log of Windows 7, I found this error code http://images.siteface.net/siteface//tmpDirs/243DADCBA5A0EE1C1497D58D578D0A24/1_Visionaire_error.jpgNext... reinstalled the drivers update:Visionaire Player works fine, I have only this one line that does not convince me "no uniform pass in shader"Visionaire Editor works using 50% of my CPU only in TAB that contain or may contain images (OBJECTSCENE, CHARACTERS, ANIMATION etc)Searching in the Visionaire Editor Log file I've found this[quote]17:40:44: Initializing COM...17:40:44: OK.17:40:44: Loading 'C:\Program Files\Visionaire Studio 4\xml/language.2.english.xml'...17:40:44: Loading 'C:\Program Files\Visionaire Studio 4\xml/images.xml'...17:40:44: Loading image-list "etypedata"...17:40:44: 17:40:44: Log file for Visionaire Editor 4.2.5, full version (Build: 1185)17:40:44: Current date: 26.06.16 17:4017:40:44: -------------------------------------17:40:44: Loading 'C:\Program Files\Visionaire Studio 4\xml\structures.xml'...17:40:44: Loading 'C:\Program Files\Visionaire Studio 4\xml\actions.xml'...17:40:44: Loading 'C:\Program Files\Visionaire Studio 4\xml\actionParts.xml'...17:40:44: Finished sorting action parts.17:40:44: Loading valid links...17:40:44: Successfully loaded 'xml/validlinks.xml'.17:40:44: 0(42) : warning C7011: implicit cast from "int" to "float"0(42) : warning C7011: implicit cast from "int" to "float"0(42) : warning C7011: implicit cast from "int" to "float"0(42) : warning C7011: implicit cast from "int" to "float"0(132) : warning C7011: implicit cast from "int" to "float"0(132) : warning C7011: implicit cast from "int" to "float"0(136) : warning C7011: implicit cast from "int" to "float"0(136) : warning C7011: implicit cast from "int" to "float"17:40:44: 0(42) : warning C7011: implicit cast from "int" to "float"0(42) : warning C7011: implicit cast from "int" to "float"0(42) : warning C7011: implicit cast from "int" to "float"0(42) : warning C7011: implicit cast from "int" to "float"0(132) : warning C7011: implicit cast from "int" to "float"0(132) : warning C7011: implicit cast from "int" to "float"0(136) : warning C7011: implicit cast from "int" to "float"0(136) : warning C7011: implicit cast from "int" to "float"17:40:44: Fragment info-------------0(42) : warning C7011: implicit cast from "int" to "float"0(42) : warning C7011: implicit cast from "int" to "float"0(42) : warning C7011: implicit cast from "int" to "float"0(42) : warning C7011: implicit cast from "int" to "float"0(132) : warning C7011: implicit cast from "int" to "float"0(132) : warning C7011: implicit cast from "int" to "float"0(136) : warning C7011: implicit cast from "int" to "float"0(136) : warning C7011: implicit cast from "int" to "float"0(117) : warning C7011: implicit cast from "int" to "float"0(118) : warning C7011: implicit cast from "int" to "float"17:41:09: Serialization finished. Needed time: 136 ms17:41:09: SetupParents finished. Needed time: 3 ms17:41:09: SortLinks finished. Needed time: 18 ms17:41:14: Script local label if useTableToolbar then label = "#ScenesAndMenus" else label = nil end objectList("VisOb took 921 ms17:41:14: Using Framebuffer with texture.[/quote]The warning lines also were present before the upgrade. It seems that this has revealed a problem that now, even doing the downgrade of the drivers, does not disappear.I also noticed that the massive CPU usage occurs when invoked from visionaire the command "using framebuffer with texture" All this can help you understand how to solve my problem?

Ich habe mir das Shader-Script angeschaut und NICHTS verstanden. Weder, wie ich was anlegen muss - und überhaupt - noch was ich ändern muss, um irgendwas Bestimmtes hinzubekommen. Eine kleine Hilfe auf Deutsch wäre schon ganz nett... ;-) Für meine Bedürfnisse ist es außerdem "Overkill", weil ich ja keine eigenen Lichtquellen setzen möchte (das müsste ich, wenn ich nur EINE Shaderlichtquelle für die Taschenlampe verwende - alles andere ist dann nämlich total schwarz). Deshalb werde ich das Script nicht verwenden.Meine "Primitiv"-Version funktioniert ja eigentlich - ich weiß nur nicht, wie ich Visionaire klarmache, dass es regelmäßig die Ausrichtung des aktiven Charakters überprüft und immer neu anpasst. Hat - glaube ich - etwas mit "localer" Variable zu tun, deshalb habe ich das "local" überall weggenommen, damit die Variable IMMER und im ganzen Spiel gültig ist. Mal sehen, ob das stimmt...Allerdings hat sie noch den Nachteil, dass mein Overlay-Objekt mindestens doppelt so groß wie meine Kulisse sein muss (in Pixeln), damit ich nach rechts und links laufen kann. Ich weiß, dass ich die Maske kleiner anlegen und danach skalieren kann, weiß nur nicht wie.

Es gibt übrigens einen shader, der eine Taschenlampe simulieren kann. Such mal hier im forum nach shaderlamp. Ist aber unglaublich konfus zu konfigurieren.

Or am i missing the point, and you're saying the shader effect ive applied to the scene object image wont move?I know its not really applied to the image, but to the object itself, but the image moves with the object, so i cant see why the shader effect wouldnt go with it too, unless its position is just calculated once at the beggining of the scene, using the object as reference and its not actually linked to the object?Oh for a manual or better education... (just kidding Visionaire team, i know you work your tushes off.)