glcore | dependency OpenGL support library | Graphics library

The solution for me was to explictly point to the correct shared libraries using: LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ qtcreator

See https://stackoverflow.com/a/52422726/2135504

I had the exact same problem. I fixed it by moving my pass in the second subshader into the first subshader, just below the first pass, and deleting my second subshader.

I'm pretty new to Unity, but I think it's because Unity only loads one subshader. It's likely that different subshaders are designed to give you the flexibility to handle different situations or platforms, but only one will be active at a time. Try putting both passes into the same subshader and see if that fixes your problem.

The solution to this strange issue is analogous to my other post regarding context menus inside of a QGraphicsScene. To fix this behavior, simply set the setWindowFlags(Qt::BypassGraphicsProxyWidget) on either the parent window widget or the sub-mainwindow itself. If you do it on the parent widget, it'll implicitly apply it to the QMainWindow. Anytime there seems to be an issue in a QGraphicsScene, setting that above flag seems to solve most bugs/issues.

glDrawArrays() exists since OpenGL 1.1. This version was supported by Windows, without the need of getting a function pointer to it. Just use it as any other common function of your preferred language.

In fact, trying to get a function pointer with "GetProcAddress()" method may return a null pointer, which leads to a crash as soon as it get called.

Being that said, some graphics drivers may expose a function pointer for each OGL 1.1 command. Thus, using GetProcAddress may return a valid pointer. That explains why your code works in some machines but not in others.

My advise is: don't use function pointers for commands existing in OGL 1.1

How can I solve the problem so I can run Unity smoothly and without having to go to force-glcore ?

There are other things you can try.

1.Use DirectX9 instead of DirectX11. The default on the new Unity verions is DirectX11.

Go to File ---> Build Settings... ---> Player Settings ---> Other Settings then un-check the Auto Graphics API for Windows API checkbox. From there drag and move Direct3D9 above Direct3D11 click Apply and restart the Unity Editor.

If Direct3D9 is already above Direct3D11 then move Direct3D11 above Direct3D9.

2.If #1 doesn't work, try other graphics API. You can try other 3 graphics API such as Direct3D9, Vulkan and OpenGL Core.

These are hidden and you must click the + sign then manually add them to the menu then drag them to the top.

Then you can chose which one to add and then drag them to the top to force Unity use them.

Once of these should work for you. Chose the one that works the most. You don't need -force-glcore when opening Unity to use this. Your issue is mostly a driver issue sometimes, a workaround like this solves it until the driver is fixed.

Unity provides a handful of built-in values for your shaders: things like current object’s transformation matrices, time etc.

You just use them in ShaderLab like you’d use any other property, the only difference is that you don’t have to declare it somewhere - they are “built in”.

https://docs.unity3d.com/455/Documentation/Manual/SL-BuiltinValues.html

there is a clever way of giving you 4 variations of the value, potentially saving you a multiply operation by re-using the pre-multiplied value for every pixel being rendered. There are 4 values available.

eventually found the solution. compilation can be done by passing -u _nv021glcore -u _nv013glcore which brings back the failed opcode. To solve this also need to startx with -- +iglx to enable indirect rendering which seems to be disabled by default these days as it seems to be considered legacy openGL

The built-in value _Time is a float4 so you have to pick one of the components depending on the time scale you want:

_Time float4 (t/20, t, t*2, t*3), use to animate things inside the shaders.

for example #define T (_Time.y/3.+5.).

Another thing is the * operator for float2x2 represents a component-wise product of 2 matrices. For vector-matrix/matrix-matrix product you should use the mul function.

So in the rot function you should have p =mul(p, float2x2(sc.y,-sc.x,sc));.

For more info on this you can go to: https://en.wikibooks.org/wiki/Cg_Programming/Vector_and_Matrix_Operations.

So the answer should probably be: build SFML 2.4.2 yourself. But using my self-built SFML also produces errors while compiling simple SFML example code, this time during linking stage due to some known bug in Ubuntu. There's a simple fix though: