# Using float64 with Makie attribute 'shininess' gives error

**URL:** https://discourse.julialang.org/t/using-float64-with-makie-attribute-shininess-gives-error/130293
**Category:** Visualization
**Tags:** makie
**Created:** [June 28, 2025, 9:13am UTC](https://discourse.julialang.org/t/using-float64-with-makie-attribute-shininess-gives-error/130293 "2025-06-28T09:13:30Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![fruno](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fruno/32/5013_2.png) [@fruno](https://discourse.julialang.org/u/fruno)
#### Post date: [June 28, 2025, 9:13am UTC](https://discourse.julialang.org/t/using-float64-with-makie-attribute-shininess-gives-error/130293/1 "2025-06-28T09:13:30Z")

</div>

Hi,

Since the update to Makie 0.24, `shininess` appears to require floats (Float32).

For Makie 0.23 GLMakie supported doubles (Float64), but CairoMakie did not (for default versions of the backends). Now neither supports Float64.

I can of course use Float32 for this specific attribute for now, but I guess that should not be needed long-term.

GLMakie:

```julia
julia> meshscatter!(Point3(0.,0.,0.), marker = Sphere(Point3f(0, 0, 0), 0.5), shininess = 50.)
ERROR: shininess in uniforms is a banned type: Float64
...

```

Packages:

```julia
(jl_CK44Hd) pkg> st
Status `/private/var/folders/0l/8dbr8drn1n5176ph_4q8jkjr0000gp/T/jl_CK44Hd/Project.toml`
  [e9467ef8] GLMakie v0.13.1
⌅ [ee78f7c6] Makie v0.24.1

```

Julia version:

```julia
julia> versioninfo()
Julia Version 1.11.5
Commit 760b2e5b739 (2025-04-14 06:53 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: macOS (arm64-apple-darwin24.0.0)
  CPU: 10 × Apple M1 Max
  WORD_SIZE: 64
  LLVM: libLLVM-16.0.6 (ORCJIT, apple-m1)
Threads: 1 default, 0 interactive, 1 GC (on 8 virtual cores)
Environment:
  JULIA_EDITOR = code -g

```

Thanks in advance for considering this!

---

<div class="post-metadata">

### Author: ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)
#### Post date: [June 28, 2025, 9:43am UTC](https://discourse.julialang.org/t/using-float64-with-makie-attribute-shininess-gives-error/130293/2 "2025-06-28T09:43:40Z")

</div>

oh, that means there’s a `convert_attribute(shininess, ::key"shininess") = Float32(shininess)` missing.  
Would you be able to PR this and add a test checking for `plot.shininess[]::Float32`?

---

<div class="post-metadata">

### Author: ![fruno](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fruno/32/5013_2.png) [@fruno](https://discourse.julialang.org/u/fruno)
#### Post date: [June 28, 2025, 11:08am UTC](https://discourse.julialang.org/t/using-float64-with-makie-attribute-shininess-gives-error/130293/3 "2025-06-28T11:08:37Z")

</div>

Looking at how `backlight` is handled with respect to types, I added

```julia
convert_attribute(value, ::key"shininess") = Float32(value)

```

in `conversions.jl`, which seems to make it work.

Would that be the way to fix the issue?

---

<div class="post-metadata">

### Author: ![sdanisch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sdanisch/32/1406_2.png) [@sdanisch](https://discourse.julialang.org/u/sdanisch)
#### Post date: [June 28, 2025, 3:48pm UTC](https://discourse.julialang.org/t/using-float64-with-makie-attribute-shininess-gives-error/130293/4 "2025-06-28T15:48:48Z")

</div>

Yes! That looks correct!

---

<div class="post-metadata">

### Author: ![fruno](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fruno/32/5013_2.png) [@fruno](https://discourse.julialang.org/u/fruno)
#### Post date: [July 8, 2025, 2:35pm UTC](https://discourse.julialang.org/t/using-float64-with-makie-attribute-shininess-gives-error/130293/5 "2025-07-08T14:35:05Z")

</div>

My skillset regarding Github is unfortunately lacking, so I instead updated an [existing issue](https://github.com/MakieOrg/Makie.jl/issues/4060) (which appears to be directly related to the same problem). At least the (potential) solution is then “documented”.
