[OGL-3D Vision Wrapper] is now Open Source.
Hi, I kept saying for some time now that I will release the source code for the wrapper. Today is the big day that I do that:) I cleaned up the code a bit (is not a complete mess anyway) as you will see, but some "hacks" are still in place and my favorite "extern this and extern that". A refactoring will surely get rid of some things like this;)) The code is written in C AND C++ (as you will see). Source Code can be found on GitHub: [url=https://github.com/helifax/OGL-3DVision-Wrapper]https://github.com/helifax/OGL-3DVision-Wrapper[/url] You can fork it if you want to but I WOULD REALLY APPRECIATE if any fixes or improvements are merged back to the master:) Besides this I can't really say anything else:) If you are interested in playing with it and have trouble let me know:) Cheers!
Hi,

I kept saying for some time now that I will release the source code for the wrapper. Today is the big day that I do that:)

I cleaned up the code a bit (is not a complete mess anyway) as you will see, but some "hacks" are still in place and my favorite "extern this and extern that". A refactoring will surely get rid of some things like this;))

The code is written in C AND C++ (as you will see).
Source Code can be found on GitHub: https://github.com/helifax/OGL-3DVision-Wrapper

You can fork it if you want to but I WOULD REALLY APPRECIATE if any fixes or improvements are merged back to the master:)


Besides this I can't really say anything else:) If you are interested in playing with it and have trouble let me know:)

Cheers!

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

#1
Posted 02/07/2015 02:21 PM   
Nvidia need to hire you!
Nvidia need to hire you!

#2
Posted 02/07/2015 02:29 PM   
Cheerz!
Cheerz!

#3
Posted 02/07/2015 10:26 PM   
Awesome! I'll definitely have to take a look at this :)
Awesome! I'll definitely have to take a look at this :)

2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit

Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD

Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword

#4
Posted 02/08/2015 01:20 AM   
This is looking pretty good (I just need to work out what OpenGL games I have that I can try it out with). I just have one concern about the license agreement. It looks almost like the standard MIT license, but it has one additional clause: [quote]If you use this software in any public release, please cite and credit the author of this software.[/quote] This extra clause seems harmless enough at first glance, but it actually has the consequence of making this project incompatible with any other project using the General Public License, which explicitly forbids further restrictions such as that one (the intent in the GPL is not to forbid mixing code from other open source projects - it is to make it impossible to use GPL licensed code with a closed source project and to ensure that the freedoms granted by the GPL cannot be removed. The compatibility issues with other free licenses are an unfortunate side-effect). I'm not a lawyer, but I'm also concerned that that clause will turn out to be viral - e.g. if I were to copy even a single line of code from this wrapper (one that I did not write myself) into 3Dmigoto I would also have to add this clause to that project to comply with this license, thereby also making 3Dmigoto incompatible with GPL licensed code. I doubt that is your intention, but plenty of other open source projects have been bitten by exactly these type of licensing compatibility issues in the past, and it's much better to change the license now (while you are the only copyright holder) rather than later (when you may find you need to contact everyone who has contributed to the project to obtain their permission (or their employer's permission) to re-license their code, or remove it from the tree). I would suggest just dropping the extra clause and using the standard MIT license. It's a good license that already requires attribution for "all copies of substantial portions of the software" and MIT licensed code can be used freely in almost all open source and proprietary projects. 3Dmigoto uses the standard MIT license, so it would be suitable to enable sharing code back and forth between the two without licensing concerns. Another concern I have about this clause is that the attributions might get out of hand. For now it's easy enough since you are the only author so there is only one name to cite, but for instance - if 3Dmigoto contained a similar clause then anyone releasing it as part of a fix would have to cite Chiri, bo3b, Flugan and myself. As it is, they only need to include the 3Dmigoto copyright notice which will list the major authors (although I realise this may not be happening at the moment - I'll raise that concern in the 3Dmigoto thread), and other contributions can be acknowledged elsewhere (e.g. a thanks note in the changelog, or the authorship information in the public git history).
This is looking pretty good (I just need to work out what OpenGL games I have that I can try it out with). I just have one concern about the license agreement. It looks almost like the standard MIT license, but it has one additional clause:

If you use this software in any public release, please cite and credit
the author of this software.


This extra clause seems harmless enough at first glance, but it actually has the consequence of making this project incompatible with any other project using the General Public License, which explicitly forbids further restrictions such as that one (the intent in the GPL is not to forbid mixing code from other open source projects - it is to make it impossible to use GPL licensed code with a closed source project and to ensure that the freedoms granted by the GPL cannot be removed. The compatibility issues with other free licenses are an unfortunate side-effect).

I'm not a lawyer, but I'm also concerned that that clause will turn out to be viral - e.g. if I were to copy even a single line of code from this wrapper (one that I did not write myself) into 3Dmigoto I would also have to add this clause to that project to comply with this license, thereby also making 3Dmigoto incompatible with GPL licensed code.

I doubt that is your intention, but plenty of other open source projects have been bitten by exactly these type of licensing compatibility issues in the past, and it's much better to change the license now (while you are the only copyright holder) rather than later (when you may find you need to contact everyone who has contributed to the project to obtain their permission (or their employer's permission) to re-license their code, or remove it from the tree).

I would suggest just dropping the extra clause and using the standard MIT license. It's a good license that already requires attribution for "all copies of substantial portions of the software" and MIT licensed code can be used freely in almost all open source and proprietary projects. 3Dmigoto uses the standard MIT license, so it would be suitable to enable sharing code back and forth between the two without licensing concerns.


Another concern I have about this clause is that the attributions might get out of hand. For now it's easy enough since you are the only author so there is only one name to cite, but for instance - if 3Dmigoto contained a similar clause then anyone releasing it as part of a fix would have to cite Chiri, bo3b, Flugan and myself. As it is, they only need to include the 3Dmigoto copyright notice which will list the major authors (although I realise this may not be happening at the moment - I'll raise that concern in the 3Dmigoto thread), and other contributions can be acknowledged elsewhere (e.g. a thanks note in the changelog, or the authorship information in the public git history).

2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit

Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD

Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword

#5
Posted 02/09/2015 06:10 AM   
One other thing that just occurred to me - the license file should not be named EULA.txt, as that suggests that it only applies to "End Users". For open source projects a more generic name like LICENSE.txt is probably a better choice.
One other thing that just occurred to me - the license file should not be named EULA.txt, as that suggests that it only applies to "End Users". For open source projects a more generic name like LICENSE.txt is probably a better choice.

2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit

Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD

Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword

#6
Posted 02/09/2015 07:03 AM   
[quote="DarkStarSword"]One other thing that just occurred to me - the license file should not be named EULA.txt, as that suggests that it only applies to "End Users". For open source projects a more generic name like LICENSE.txt is probably a better choice.[/quote] Oops yeah:)) I'll remove that one;)) That was put there on the 1st build release;)) Forgot to remove it when I put it open as Open Source;)) I will remove those line and rename the EULA to License ;)) Big thx for these catches ^_^ :D Edit: Done!
DarkStarSword said:One other thing that just occurred to me - the license file should not be named EULA.txt, as that suggests that it only applies to "End Users". For open source projects a more generic name like LICENSE.txt is probably a better choice.


Oops yeah:)) I'll remove that one;)) That was put there on the 1st build release;)) Forgot to remove it when I put it open as Open Source;))

I will remove those line and rename the EULA to License ;)) Big thx for these catches ^_^ :D

Edit: Done!

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

#7
Posted 02/09/2015 11:20 AM   
Great, thanks for fixing that :) Licensing is always so dreary, but it does form the legal basis that gives open source it's strength, so it's definitely important to try to get right.
Great, thanks for fixing that :) Licensing is always so dreary, but it does form the legal basis that gives open source it's strength, so it's definitely important to try to get right.

2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit

Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD

Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword

#8
Posted 02/09/2015 12:54 PM   
[quote="DarkStarSword"]Great, thanks for fixing that :) Licensing is always so dreary, but it does form the legal basis that gives open source it's strength, so it's definitely important to try to get right.[/quote] Completely agree ! ;))
DarkStarSword said:Great, thanks for fixing that :) Licensing is always so dreary, but it does form the legal basis that gives open source it's strength, so it's definitely important to try to get right.


Completely agree ! ;))

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

#9
Posted 02/09/2015 12:57 PM   
How does 3Dmigoto MIT license relate to nektra which has GPL. I'm just a little confused.
How does 3Dmigoto MIT license relate to nektra which has GPL. I'm just a little confused.

Thanks to everybody using my assembler it warms my heart.
To have a critical piece of code that everyone can enjoy!
What more can you ask for?

donations: ulfjalmbrant@hotmail.com

#10
Posted 02/26/2015 09:50 PM   
GPL licensing comes into effect on distribution - so, when 3Dmigoto is distributed statically linked against the Deviare library you are correct that it will be covered by the GPL as a whole and we have to comply with the GPL in that situation (and our source is available so we are). But that doesn't stop us releasing our own code under the MIT license as well if we choose to do so. If someone were to take our code and either remove the Deviare library or purchase a commercial Deviare license they could use the rest of our code under the MIT license. Likewise if they only take part of our code that does not use Deviare they would not be affected by the Deviare license. I added a COPYING.txt to the 3Dmigoto repository to clarify this situation.
GPL licensing comes into effect on distribution - so, when 3Dmigoto is distributed statically linked against the Deviare library you are correct that it will be covered by the GPL as a whole and we have to comply with the GPL in that situation (and our source is available so we are).

But that doesn't stop us releasing our own code under the MIT license as well if we choose to do so. If someone were to take our code and either remove the Deviare library or purchase a commercial Deviare license they could use the rest of our code under the MIT license. Likewise if they only take part of our code that does not use Deviare they would not be affected by the Deviare license.

I added a COPYING.txt to the 3Dmigoto repository to clarify this situation.

2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit

Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD

Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword

#11
Posted 02/27/2015 12:12 AM   
Scroll To Top