• Advertisement
Sign in to follow this  

Unity [.net] OpenGL under-represented?

This topic is 4505 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Dotnet OpenGL developers are now a minority in a minority it seems. But I see no real reason for that. Maybe it is just that the OpenGL bindings are not as easily available or known as managed directX. Or is it just my imagination? And little request to the mods: The forum title sais it is a place to discuss .NET, including managed directX and C#. I think it would be better to say ".NET and Mono, including C#, managed directX, OpenGL and other API bindings" instead. This would focus the OpenGL/dotnet discussion in a single forum and not spread it to 3(this forum, OpenGL and Nehe) and make OpenGL bindings like Tao more popular in the gamedev community.

Share this post


Link to post
Share on other sites
Advertisement
Quote:
Original post by Xanthos
Maybe it is just that the OpenGL bindings are not as easily available or known as managed directX.

Or maybe it's the fact that they're bindings. Or maybe it's the likelihood of an OpenGL user being suspicious of any and everything Microsoft. Or maybe it's because you can never be sure when the Tao Framework page will actually be up?

Nobody knows, really.

Quote:
I think it would be better to say ".NET and Mono, including C#, managed directX, OpenGL and other API bindings" instead.

That's a mouthful! What about VB.NET? IronPython? COBOL.NET? I agree that the current description leaves something to be desired, but where to we find the balance between completeness and conciseness? Just something to think about.

Quote:
This would focus the OpenGL/dotnet discussion in a single forum and not spread it to 3(this forum, OpenGL and Nehe)...

Question: why is there always such a strong negative reaction against combining the OpenGL and NeHe forums? I really don't think changing the forum description would change the forum member behavior, but YMMV.


Note: These are personal opinions, not policy or anything. I'm not saying the current situation is perfect; I'm inviting more speculation and analysis.

Share this post


Link to post
Share on other sites
Quote:
Original post by Oluseyi
Quote:
I think it would be better to say ".NET and Mono, including C#, managed directX, OpenGL and other API bindings" instead.

That's a mouthful! What about VB.NET? IronPython? COBOL.NET? I agree that the current description leaves something to be desired, but where to we find the balance between completeness and conciseness? Just something to think about.


I have nothing against other languages/libs in the list.

And managed directX is also not much more than a binding, it`s just that it is currently in the list and OpenGL not. I gives a wrong impression to beginners IMO.

Maybe it would be better to move all managed directX discussions to the directX forum instead.



Share this post


Link to post
Share on other sites
Hi,

If you want to use .Net with OpenGL you should try VC++ .Net perhaps? You can attach an OpenGL Rendering context to a .Net form this way. Its not that difficult. I have only moved to using .Net forms instead of Win32 windows. It makes adding GUI components easy.

Share this post


Link to post
Share on other sites
Quote:
Original post by Xanthos
The forum title sais it is a place to discuss .NET, including managed directX and C#. I think it would be better to say ".NET and Mono, including C#, managed directX, OpenGL and other API bindings" instead.


I think that the description says too much now. IMO it should only say "Discussion about the .NET framework and .NET languages"

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Quote:
Original post by Xanthos
And managed directX is also not much more than a binding, it`s just that it is currently in the list and OpenGL not.


I hate to side-track the topic slightly, but I have to disagree completely. Tao simply binds the procedural OpenGL API, while MDX creates a high level wrapper chock full of OO stuff.

As for it not being listed in the description... I think the description should be shortened to ".NET/Mono game development forum."

Share this post


Link to post
Share on other sites
Quote:
Original post by Cacks
If you want to use .Net with OpenGL you should try VC++ .Net perhaps? You can attach an OpenGL Rendering context to a .Net form this way. Its not that difficult. I have only moved to using .Net forms instead of Win32 windows. It makes adding GUI components easy.


I think you misunderstood the topic of this thread. I did not search for advise how to use OpenGL with .NET.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By khawk
      Watch the latest from Unity.
       
    • By GytisDev
      Hello,
      without going into any details I am looking for any articles or blogs or advice about city building and RTS games in general. I tried to search for these on my own, but would like to see your input also. I want to make a very simple version of a game like Banished or Kingdoms and Castles,  where I would be able to place like two types of buildings, make farms and cut trees for resources while controlling a single worker. I have some problem understanding how these games works in the back-end: how various data can be stored about the map and objects, how grids works, implementing work system (like a little cube (human) walks to a tree and cuts it) and so on. I am also pretty confident in my programming capabilities for such a game. Sorry if I make any mistakes, English is not my native language.
      Thank you in advance.
    • By Ovicior
      Hey,
      So I'm currently working on a rogue-like top-down game that features melee combat. Getting basic weapon stats like power, weight, and range is not a problem. I am, however, having a problem with coming up with a flexible and dynamic system to allow me to quickly create unique effects for the weapons. I want to essentially create a sort of API that is called when appropriate and gives whatever information is necessary (For example, I could opt to use methods called OnPlayerHit() or IfPlayerBleeding() to implement behavior for each weapon). The issue is, I've never actually made a system as flexible as this.
      My current idea is to make a base abstract weapon class, and then have calls to all the methods when appropriate in there (OnPlayerHit() would be called whenever the player's health is subtracted from, for example). This would involve creating a sub-class for every weapon type and overriding each method to make sure the behavior works appropriately. This does not feel very efficient or clean at all. I was thinking of using interfaces to allow for the implementation of whatever "event" is needed (such as having an interface for OnPlayerAttack(), which would force the creation of a method that is called whenever the player attacks something).
       
      Here's a couple unique weapon ideas I have:
      Explosion sword: Create explosion in attack direction.
      Cold sword: Chance to freeze enemies when they are hit.
      Electric sword: On attack, electricity chains damage to nearby enemies.
       
      I'm basically trying to create a sort of API that'll allow me to easily inherit from a base weapon class and add additional behaviors somehow. One thing to know is that I'm on Unity, and swapping the weapon object's weapon component whenever the weapon changes is not at all a good idea. I need some way to contain all this varying data in one Unity component that can contain a Weapon field to hold all this data. Any ideas?
       
      I'm currently considering having a WeaponController class that can contain a Weapon class, which calls all the methods I use to create unique effects in the weapon (Such as OnPlayerAttack()) when appropriate.
    • By Vu Chi Thien
      Hi fellow game devs,
      First, I would like to apologize for the wall of text.
      As you may notice I have been digging in vehicle simulation for some times now through my clutch question posts. And thanks to the generous help of you guys, especially @CombatWombat I have finished my clutch model (Really CombatWombat you deserve much more than a post upvote, I would buy you a drink if I could ha ha). 
      Now the final piece in my vehicle physic model is the differential. For now I have an open-differential model working quite well by just outputting torque 50-50 to left and right wheel. Now I would like to implement a Limited Slip Differential. I have very limited knowledge about LSD, and what I know about LSD is through readings on racer.nl documentation, watching Youtube videos, and playing around with games like Assetto Corsa and Project Cars. So this is what I understand so far:
      - The LSD acts like an open-diff when there is no torque from engine applied to the input shaft of the diff. However, in clutch-type LSD there is still an amount of binding between the left and right wheel due to preload spring.
      - When there is torque to the input shaft (on power and off power in 2 ways LSD), in ramp LSD, the ramp will push the clutch patch together, creating binding force. The amount of binding force depends on the amount of clutch patch and ramp angle, so the diff will not completely locked up and there is still difference in wheel speed between left and right wheel, but when the locking force is enough the diff will lock.
      - There also something I'm not sure is the amount of torque ratio based on road resistance torque (rolling resistance I guess)., but since I cannot extract rolling resistance from the tire model I'm using (Unity wheelCollider), I think I would not use this approach. Instead I'm going to use the speed difference in left and right wheel, similar to torsen diff. Below is my rough model with the clutch type LSD:
      speedDiff = leftWheelSpeed - rightWheelSpeed; //torque to differential input shaft. //first treat the diff as an open diff with equal torque to both wheels inputTorque = gearBoxTorque * 0.5f; //then modify torque to each wheel based on wheel speed difference //the difference in torque depends on speed difference, throttleInput (on/off power) //amount of locking force wanted at different amount of speed difference, //and preload force //torque to left wheel leftWheelTorque = inputTorque - (speedDiff * preLoadForce + lockingForce * throttleInput); //torque to right wheel rightWheelTorque = inputTorque + (speedDiff * preLoadForce + lockingForce * throttleInput); I'm putting throttle input in because from what I've read the amount of locking also depends on the amount of throttle input (harder throttle -> higher  torque input -> stronger locking). The model is nowhere near good, so please jump in and correct me.
      Also I have a few questions:
      - In torsen/geared LSD, is it correct that the diff actually never lock but only split torque based on bias ratio, which also based on speed difference between wheels? And does the bias only happen when the speed difference reaches the ratio (say 2:1 or 3:1) and below that it will act like an open diff, which basically like an open diff with an if statement to switch state?
      - Is it correct that the amount of locking force in clutch LSD depends on amount of input torque? If so, what is the threshold of the input torque to "activate" the diff (start splitting torque)? How can I get the amount of torque bias ratio (in wheelTorque = inputTorque * biasRatio) based on the speed difference or rolling resistance at wheel?
      - Is the speed at the input shaft of the diff always equals to the average speed of 2 wheels ie (left + right) / 2?
      Please help me out with this. I haven't found any topic about this yet on gamedev, and this is my final piece of the puzzle. Thank you guys very very much.
  • Advertisement