Mac OS X progress

Can you post the list of supported extensions and the reported version (as returned by GetString)? The errors about the GL version are probably a result of mis-parsing the version string in GLHelper.cs:397 (BuildExtensionList method).

Edit: I'm working on the text issues on Mono (which are blocking the 0.9.2 branch).

Sweet.

The output from Simple FBO should look like this. It's just a bunch of random triangles with random colors to fill the textures, so your result will vary a bit.

Not sure about the GLSL Fractal, it might have fallen back to software and you need to wait 5 minutes until the first frame is done. According to the info a quick google search turned up on the graphics chip it supports GL 1.4, so I'm quite impressed it runs at all.

Good to hear that OpenAL is not complaining ^^

Edit: What Mono version is installed? (just to avoid Mono 1.x.x versions to cause any conflicts, there have been some iirc which might explain the problem with the VBO example)

Ok, sorry this took so long to post. It exposed another bug that I need to deal with. Right now the call to CGDisplayAvailableModes to list the graphics modes that the display supports crashes, unless a Windows.Forms.Form is created first. So it looks like there's some initialization that Mono's OSX driver does that I am not doing right now. Will look into it ASAP.

Vendor: Intel Inc.
Renderer: Intel GMA 950 OpenGL Engine
Version: 1.2 APPLE-1.4.56
Extensions: GL_ARB_transpose_matrix GL_ARB_vertex_program GL_ARB_vertex_blend GL_ARB_window_pos GL_ARB_shader_objects GL_ARB_vertex_shader GL_EXT_multi_draw_arrays GL_EXT_clip_volume_hint GL_EXT_rescale_normal GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_gpu_program_parameters GL_APPLE_client_storage GL_APPLE_specular_vector GL_APPLE_transform_hint GL_APPLE_packed_pixels GL_APPLE_fence GL_APPLE_vertex_array_object GL_APPLE_vertex_program_evaluators GL_APPLE_element_array GL_APPLE_flush_render GL_NV_texgen_reflection GL_NV_light_max_exponent GL_IBM_rasterpos_clip GL_SGIS_generate_mipmap GL_ARB_shading_language_100 GL_ARB_texture_border_clamp GL_ARB_multitexture GL_ARB_texture_env_add GL_ARB_texture_cube_map GL_ARB_texture_env_dot3 GL_ARB_texture_env_combine GL_ARB_texture_compression GL_ARB_texture_mirrored_repeat GL_ARB_shadow GL_ARB_depth_texture GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_point_sprite GL_ARB_texture_non_power_of_two GL_ARB_vertex_buffer_object GL_ARB_pixel_buffer_object GL_EXT_framebuffer_object GL_EXT_texture_rectangle GL_ARB_texture_rectangle GL_EXT_texture_env_add GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_texture_lod_bias GL_EXT_abgr GL_EXT_bgra GL_EXT_stencil_wrap GL_EXT_texture_filter_anisotropic GL_EXT_separate_specular_color GL_EXT_secondary_color GL_EXT_blend_func_separate GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_texture_compression_s3tc GL_EXT_texture_compression_dxt1 GL_EXT_blend_equation_separate GL_EXT_packed_depth_stencil GL_APPLE_flush_buffer_range GL_APPLE_ycbcr_422 GL_APPLE_texture_range GL_APPLE_pixel_buffer GL_NV_blend_square GL_ATI_texture_env_combine3 GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod
ShadingLanguageVersion: 1.10

Responses to other things:
I saved and tested the Poems.txt file with three different line endings, dos (\r\n), unix (\n) and mac (\r) as saved in vim. dos and unix give the same result, and the mac setting is even worse as it puts all the text on the same line. None of them give good results.

The FBO results look just like that, with some randomness, so that's good.

Edit: I am using Mono 2.0.1.

GL_ARB_shader_objects
GL_ARB_vertex_shader
GL_ARB_fragment_shader

It appears to support GLSL 1.1, when looking at this I cannot get rid of the feeling that this driver is heavily work-in-progress. E.g. GL_EXT_framebuffer_object is GL 1.5, although version reports something different.

I am going on thanksgiving vacation in two days, so I probably won't be available to comment or work on this until after thanksgiving weekend. After that I expect to hit the ground running on getting WinForms support working.

Okay, I am back. I just upgraded my mac mini to 2 GB of ram from 512 MB too, so it will make development on it a lot more tolerable.

I have no objections to that. What needs to be done to make GLWidget work with OSX? Do you just need the AGL wrapper codes or something else in addition?

GLWidget is a single cs file that just needs the right calls to setup the context. I've never messed with the AGL but I don't expect it to be too different from the WGL and GLX.
In GTK there is a realized event, and when this first happens is when I initialize the context. This ensures that the proper handles have all been initialized beforehand.

I'd love to test out the new functionality on my Mac, but I currently have a few higher priority items. I'll try to test it soon.

Glad to have OS X support in OpenTK! Thanks!

Ok, I have attached the compiled binaries for the example launcher. I packed them into a finder friendly application, so they should be able to unzip and double-click. Have them test at least the examples "OpenAL: Playback" "Tutorial 2: Immediate mode" and WinForms 1 & 2. WinForms 2 will also show the driver name, which is useful to know for reports of working or non-working status. A couple examples won't work for sure, like tutorial 4 and "Test: GameWindow states," and the GLU tesselation test. The animated Julia set doesn't work on mine, but that may be because my video card sucks. Resolution changing also does not work at this point.

Yes, they will need to install mono. There is a Mac OS installer for 2.0.1 on the mono webpage, which should be adequate. I think they shouldn't need to do anything with OpenGL and OpenAL, those will already be there.

I'll try to see if this works on my MacBook Pro tonight or tomorrow.

Is there any stacktrace or output to the console?

Huh, ok interesting. Unfortunately, GameWindow is swallowing the error and disposing the CarbonGLNative object which pointed out a separate bug from the one that is making it crash in the first place. Can you look inside the Examples package (right or control- click->show package contents) and look for the Contents/Resources/debug.log and post that as an attachment?

Ok, can you give this one a shot? I have included some extra debugging information about the pixel format that is chosen, and also excluded some pixel format flags that aren't necessary. Also, what video hardware do you have and what OS version? All my tests have been on OS X 10.4.11 with an Intel GMA 950.