Fragmentarium 3DickUlus - Notes & Suggestions

[Crist-JRoger]

Wow! That's cool, cause yesterday I was thinking about reminding you of it. Really need it, especially I am putting together a 'project framework' to share with the community including some building blocks and includable fractal formulas plus a mixer for them. Not all people using frag are comfortable coding so I am trying to make a flexible fractal mixer that will make it easy to create simple hybrids.

Priceless!

For the umpteenth time I've noticed that you're reading my mind. Good luck! I am looking forward to what will happen 

[Patryk Kizny]

Since there's already a 'copy group' option, I would suggest can we add subpresets - i.e. presets only for the groups?
Would be very handy.

[3dickulus]

A preset can contain a subset only and is still valid
you can delete the ones you don't want
try "Copy Group" and paste in the text editor as the body of a preset, "build" and apply new preset
With two or more tabs/frags open you can "Copy Group" in one and "Paste Settings" in another
the "Paste Settings" function will paste text from any where
does not have to be a complete set
what ever is currently in the clipboard buffer and will try to interpret the lines as settings.

but I have a feeling you are after something like this...

Code:

#preset breakupandisolate
[Camera]
FOV = 0.6
Eye = 0,-0.733594,-0.415778
Target = -0.0108556,8.1012,0.541778
Up = 0.0194578,-0.102568,0.946549

[Raytracer]
FocalPlane = 1
Aperture = 0
InFocusAWidth = 0
ApertureNbrSides = 5
ApertureRot = 0
ApStarShaped = false
Detail = -6.6
DetailAO = -2.783133
FudgeFactor = 0.06
MaxRaySteps = 5000
MaxDistance = 10
Dither = 1
NormalBackStep = 1

etc...
#endpreset

I may add "Group to preset" button

I have seen some people's fragments with NO Default preset, although this works it is NOT recommended, the Default preset should contain ALL uniforms used in a fragment that are intended to be available in the user interface, this includes uniforms from all other #include-d fragments.

[Patryk Kizny]

I know I can do presets only for subsets in the main presets selector.
I was thinking about a separate drop-down UI widget in the group to call presets only for that group.

[3dickulus]

hmmm... that functionality exists as described above, I do not want to write "preset tracking" on a group by group basis, the code base is already very complex and I think that would just amount to too much clutter for my little brain to manage, I am just barely managing as it is, bugs, typos, flakes (bad coding practices) still get through because I just don't have the time and resources to exhaustively test everything against everything to make sure all is playing nicely together, so far so good, v1.0.15 will fix a few of these that I have found but probably have not even been noticed by users that just want to explore.

[Patryk Kizny]

Just a question - I think I could have reported that earlier.
Is there any particular reason I can't use bitmaps wider than 2K pixels?
Can you fix it in the upcoming releases? I'd love to use really large maps for backgrounds.

[Patryk Kizny]

I can also confirm that there is some mess with the maps. Please  see attached the tracer I am using.
The map for background seems to be working randomly. Most of the time Frag does confuse file references and as a result, the texture being used for BgMap comes from EnvMapDiffuse or EnvMapSpecular.
Sometimes if I want to display a map for background, the only way is to assign it to all 3 file slots I have in my raytracer. I don't think it's related to the code I am using, looks like there's something messed internally.
What also happens is that a correct map for background seem to be assigned only right after clearing texture cache, but even without any changes, the next compile messes maps.

BgMap references are in lines 483 - 540, particularly 510 in the DE-PK-1.3.frag.
Other maps used are referenced in 925 onwards.

[3dickulus]

again I stress that all required files should be included...

try putting your maps in Test-2_Files folder and make sure the sampler widget only has the filename without the full path
(yes this could use some work so users don't have to worry about it, like stripping path from name and gathering all maps together automatically when saving frags, I'm sure it finds the maps when running on your system)

when I load Test-2 after fixing the filenames in the preset...

Code:

Added texture: BgMap -> /home/uname/Fragmentarium/Examples/Include/Ditch-River_2k.hdr
Added texture: EnvMapSpecular -> /home/uname/Fragmentarium/Examples/Include/Ditch-River_2k.hdr
Added texture: EnvMapDiffuse -> /home/uname/Fragmentarium/Examples/Include/Ditch-River_Env.hdr
Setting texture to: /home/uname/Fragmentarium/Examples/Include/Ditch-River_2k.hdr
Setting texture to: /home/uname/Fragmentarium/Examples/Include/Ditch-River_2k.hdr
Setting texture to: /home/uname/Fragmentarium/Examples/Include/Ditch-River_Env.hdr
Fragment shader compiled with warnings: Fragment info
-------------
0(111) : warning C7011: implicit cast from "int" to "float"
0(115) : warning C7011: implicit cast from "int" to "float"
0(120) : warning C7011: implicit cast from "vec4" to "vec3"
0(127) : warning C7011: implicit cast from "vec4" to "vec3"
0(141) : warning C7011: implicit cast from "int" to "float"
0(149) : warning C7011: implicit cast from "int" to "float"
0(294) : warning C7011: implicit cast from "int" to "float"
0(1592) : warning C7011: implicit cast from "int" to "float"
0(1592) : warning C7011: implicit cast from "int" to "float"
0(1599) : warning C7011: implicit cast from "int" to "float"
0(1608) : warning C7011: implicit cast from "int" to "float"
0(1608) : warning C7011: implicit cast from "int" to "float"
0(1608) : warning C7011: implicit cast from "int" to "float"
0(1785) : warning C7011: implicit cast from "int" to "float"
0(1786) : warning C7011: implicit cast from "int" to "float"
0(1827) : warning C7011: implicit cast from "float" to "vec3"
0(1889) : warning C7623: implicit narrowing of type from "vec3" to "float"
0(2191) : warning C7011: implicit cast from "int" to "float"
0(2245) : warning C7011: implicit cast from "float" to "vec3"
0(2430) : warning C7011: implicit cast from "int" to "float"
0(2430) : warning C7011: implicit cast from "float" to "vec3"
0(1093) : warning C7050: "hitMat.diffuse" might be used before being initialized
0(1093) : warning C7050: "hitMat.specular" might be used before being initialized
0(1093) : warning C7050: "hitMat.diffExp" might be used before being initialized
0(1093) : warning C7050: "hitMat.specExp" might be used before being initialized
0(1093) : warning C7050: "hitMat.specMax" might be used before being initialized
0(1093) : warning C7050: "hitMat.glossiness" might be used before being initialized
0(1093) : warning C7050: "hitMat.dirt" might be used before being initialized
0(1093) : warning C7050: "hitMat.matte" might be used before being initialized
0(1292) : warning C7050: "totalLight" might be used before being initialized
0(1293) : warning C7050: "totalShadow" might be used before being initialized

Found texture in cache: /home/uname/Fragmentarium/Examples/Include/Ditch-River_2k.hdr (id: 3)
Found texture in cache: /home/uname/Fragmentarium/Examples/Include/Ditch-River_Env.hdr (id: 4)
Found texture in cache: /home/uname/Fragmentarium/Examples/Include/Ditch-River_2k.hdr (id: 3)

and Help->Clear Texture Cache...

Code:

Removing texture from cache: /home/toonfish/Fragmentarium/Examples/Include/Ditch-River_2k.hdr
Removing texture from cache: /home/toonfish/Fragmentarium/Examples/Include/Ditch-River_Env.hdr

after clearing textures and building script I get segfault  yes needs some work  but I have to figure out if it is internal (C++ side) or due to the errors that show up at frag compile time.

so...

when I remove #include "Presets-Camera-Z-Up.frag" and set the filenames in the Default preset to files that actually exist Fragmentarium-1.0.15 behaves the same as Fragmentarium-master (original version) no segfault and clear cache seems to work. From this I deduce that the problem is with "Presets-Camera-Z-Up.frag" and maybe the "might be used before being initialized" and all the "implicit cast from..." warnings.

if you can correct these warnings and put the maps in the Test-2_Files folder I will be able to test...

edit: include the Milkyway_preview.jpg file too please.
tip: setting eye or target 0,0,0 is not a good idea. afaik 0 axis has always been problematic with DEs

[3dickulus]

Just a question - I think I could have reported that earlier.
Is there any particular reason I can't use bitmaps wider than 2K pixels?
Can you fix it in the upcoming releases? I'd love to use really large maps for backgrounds.

the limit was imposed only on EXR images due to gfx card limits, I can remove the test, I understand that with GL 4.4+ sparse textures makes the limit meaningless but for compatibility with older cards I would like to leave it.

have you tried other format images as textures larger than 2048? I imposed no limit for jpg png tga bmp etc...  if you find they have the same problem then I don't think there is anything I can do about it as it's imposed in areas of code I don't have control over like Qt, GL, System libs, etc...

[Patryk Kizny]

It's same for JPGs and other formats.

[3dickulus]

very odd, I just tested a 3840x2160 jpg texture and it seems fine  v1.0.15

[Tim Emit]

Really interesting thread, thanks and thanks 3d for all the hard work. I will work my way through it and try to get to grips. : )