Water Displacement Tutorial

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

GIMP Version: 2.6.11
Operating System: Windows
OS Version: windows 7
GIMP Experience: Basic Level

I am working on this water Displacement Tutorial. I am using an 803 x 748 image.
http://gimpchat.com/viewtopic.php?f=10&t=993

I did the mirror step, then when I made a duplicate of the Mirrored image, I continued on to the water reflection map, I typed in 803 for x and 748 for Y. When I run the script, I come up with this error every time then it quits at that point.
Does anyone have any idea what could cause this. I started over 5 times and still the same message each time.

Rod · **Joined:** May 16, 2010 **Posts:** 16152

Not sure - could you post the link to the script?

Draconian · **Posted:** Tue Oct 04, 2011 1:18 pm **(#3)**

When you start to create the displacement map, does it open a separate window to do it? It should.

You might try just opening a new white image by itself and start from scratch and see if it does it again.

Also you may have had some corruption in the download process. You might also try to replace the script with a fresh copy. Just a suggestion for when you get it working again, when I did the tutorial I made several displacement maps with different settings and just save them to resize and use as needed.

I know that's not really what you wanted to hear but if I had a computer brick I'd loan it to you. (you would have to give it back soon cuz I use it frequently myself)

Rod, the link is in the tutorial she listed in her post above but here is the direct link to the registry.

http://registry.gimp.org/node/13778

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

Attachment:

dm-gen-1.2.1.scm [7.99 KiB]
Downloaded 223 times

This is the script Rod

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

thanks Drac yes it does open a separate window. I will wait a while to see if my script works for others and if not I will download it again from the site. I have done this tutorial two or three times before and it worked okay, go fig. :roll:

Draconian · **Posted:** Tue Oct 04, 2011 1:26 pm **(#6)**

I was just reading about the error mesages on the registry with the first version. Did you download version 1.2.1?

Duh! Never mind I just saw it in the post for Rod above.

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

I closed Gimp 2.6 and tried the script in 2.7 and it worked. Soooo, I guess I will live with that. thanks guys.

Rod · **Joined:** May 16, 2010 **Posts:** 16152

It is probably getting an error due to another script causing a conflict.
Most likely that is why it works for you in Gimp-2.7

saulgoode · **Posted:** Tue Oct 04, 2011 3:21 pm **(#9)**

In the script, you will find the following section of code:

Code: Select all

; Variable init
  (let* (
   (imageWidth  (car (gimp-image-width theOldImage)))
   (imageHeight (car (gimp-image-height theOldImage)))
   (mask)
   (theImage)
   (newLayer)
   (red-component 0)
   (green-component 1)
   (blue-component 2)
   (alpha-component 5)
   (i 0)
   (RGBImage)
   (num_layers 0)
   (layer_ids)
   (current_layer)
   (theDisplay)
   )

The variables mask, theImage, newLayer, RGBImage, layer_ids, current_layer, and theDisplay should all be provided with initial values. It does not matter what the initial values are ("0" will work), but they need to be provided.

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

Am I supposed to change it, I don't understand anything about the inside of a script. Mine is exactly the same as what you posted. ??

saulgoode · **Posted:** Tue Oct 04, 2011 3:44 pm **(#11)**

Try replacing that section of code with the following, saving the file, and then opening GIMP:

Code: Select all

; Variable init
  (let* (
   (imageWidth  (car (gimp-image-width theOldImage)))
   (imageHeight (car (gimp-image-height theOldImage)))
   (mask 0)
   (theImage 0)
   (newLayer 0)
   (red-component 0)
   (green-component 1)
   (blue-component 2)
   (alpha-component 5)
   (i 0)
   (RGBImage 0)
   (num_layers 0)
   (layer_ids 0)
   (current_layer 0)
   (theDisplay 0)
   )

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

I did that and saved it Saul and I still get that same error half way through the process.

paynekj · **Posted:** Tue Oct 04, 2011 4:16 pm **(#13)**

The key thing is the gimp-item-get-image in the error message. This is a function that only exists in GIMP 2.7, so you have a script that will only work using 2.7 and will not work for GIMP 2.6.

However, the script you've attached earlier doesn't have gimp-item-get-image in it at all, so you have another version of the same script somewhere that's been changed to work with 2.7

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

Ok, I will take the one out that is in 2.6 and put a new one in and see what happens.

Rod · **Joined:** May 16, 2010 **Posts:** 16152

Here is the script changed and zipped up Molly or anyone else that wants it.

Attachment:

dm-gen-1.2.1.zip [2.44 KiB]
Downloaded 180 times

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

Got the same error Rod. downloaded yours, dumped mine, rebooted gimp 2.6, ran the filter.
Error: eval: unbound variable: gimp-item-get-image

paynekj · **Posted:** Tue Oct 04, 2011 4:43 pm **(#17)**

molly wrote:

Got the same error Rod. downloaded yours, dumped mine, rebooted gimp 2.6, ran the filter.
Error: eval: unbound variable: gimp-item-get-image

My point was that you think you've dumped yours but you have another one and that one is being loaded in preference to the one you are changing.

Have a look in ALL your script folders.

It can help to have a tool that can find strings in files - my preferred text editor (TextPad) has a Find in Files option. If you're on Linux then the grep command line command is useful.

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

molly · **Joined:** Apr 07, 2010 **Posts:** 14182

OMG, your were right. I am so embarrassed. :oops:

It was in the gimp that is in Programs(x86).
Thank you so much. :tyspin

paynekj · **Posted:** Tue Oct 04, 2011 4:53 pm **(#20)**

Don't be embarrassed. It's one of those things that I think GIMP gets wrong. I feel it should report when collisions like this happen rather than silently re-defining things.