Thread: Looking for users with slower computers

So you were having problems on 64 or 32?

I'm running XP32 on an AMD 64 machine. and I have the lack of skin.

with all the negativity and bugs, i figured i post some good results(even if it isn't a low powered pc):

it seems to work fine on my laptop (hp G60, pentium t4300, 3gig's ram, 64 bit win 7 home, intel 4500m graphics).

not sure if it makes a difference, but i also have OM 0.7 also installed on this pc, and it looks like the weather location info carried over...

I got the Intel drivers installed, and no, it's still blank on my D945GCLF2... the all white does look blazing fast though...

what's new in the 0.8 graphics engine?

Oh, I forgot to mention that I tried it on Linux 32bit Ubuntu 10.04 with the open source ATI driver. OpenGL works on it, but it's missing some critical bits in the driver for things like compiz and the like.

I think the biggest improvement is hardware acceleration... wish I could test it in my truck.. ;-)

Originally Posted by CraziFuzzy

I got the Intel drivers installed, and no, it's still blank on my D945GCLF2... the all white does look blazing fast though...

Its an alpha release of something rewritten from the ground up-cut us a little slack.

Originally Posted by tripzero

what's new in the 0.8 graphics engine?

Oh, I forgot to mention that I tried it on Linux 32bit Ubuntu 10.04 with the open source ATI driver. OpenGL works on it, but it's missing some critical bits in the driver for things like compiz and the like.

compiz is openGL based (at least I thought it was)->must just not support all of the extensions compiz needs.

whats new with the 0.8 engine?:
Its 100% openGL based-but in a compile once run everywhere form.... all the ease of using regular controls like winforms or gtk with all the speed of pure hardware accelerated graphics (like your favorite 3D game). Lots of changes at the low level so that it can run really cool graphics on very low powered devices (like cell phones). Not to mention we're the first 3D capable front end (already have a dev working on 3D skins)

Yup..your totally right on the OS X version being broken

Code:

mono(15179,0xb059f000) malloc: *** error for object 0x141b784: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
Stacktrace:

  at (wrapper managed-to-native) OpenMobile.Platform.MacOS.Carbon.API.SetWindowTitleWithCFString (intptr,intptr) <0x00004>
  at (wrapper managed-to-native) OpenMobile.Platform.MacOS.Carbon.API.SetWindowTitleWithCFString (intptr,intptr) <0x00004>
  at OpenMobile.Platform.MacOS.Carbon.API.SetWindowTitle (intptr,string) <0x0001f>
  at OpenMobile.Platform.MacOS.CarbonGLNative.CreateNativeWindow (OpenMobile.Platform.MacOS.Carbon.WindowClass,OpenMobile.Platform.MacOS.Carbon.WindowAttributes,OpenMobile.Platform.MacOS.Carbon.Rect) <0x0008f>
  at OpenMobile.Platform.MacOS.CarbonGLNative..ctor (int,int,int,int,string,OpenMobile.Graphics.GraphicsMode,OpenMobile.GameWindowFlags,OpenMobile.DisplayDevice) <0x000f7>
  at OpenMobile.Platform.MacOS.MacOSFactory.CreateNativeWindow (int,int,int,int,string,OpenMobile.Graphics.GraphicsMode,OpenMobile.GameWindowFlags,OpenMobile.DisplayDevice) <0x0003e>
  at OpenMobile.NativeWindow.NativeInitialize () <0x00190>
  at OpenMobile.RenderingWindow/<>c__DisplayClass1.<RunAsync>b__0 () <0x00015>
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0x00040>

Native stacktrace:

	0   mono                                0x000c2277 mono_handle_native_sigsegv + 343
	1   mono                                0x00010e76 mono_sigsegv_signal_handler + 306
	2   libSystem.B.dylib                   0x941531fb _sigtramp + 43
	3   ???                                 0xffffffff 0x0 + 4294967295
	4   HIToolbox                           0x98b49142 _ZN6HIView26NotifySubtreeWindowChangedEP15OpaqueWindowPtrS1_h + 90
	5   HIToolbox                           0x98b4505b _ZN6HIView10AddSubViewEPS_ + 209
	6   HIToolbox                           0x98c4f5ce _ZN17HIWindowFrameView11UpdateTitleEb + 190
	7   HIToolbox                           0x98c5622d _ZN17HIWindowFrameView12EventHandlerEP25OpaqueEventHandlerCallRefP14OpaqueEventRefPv + 329
	8   HIToolbox                           0x98b2ef2f _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1567
	9   HIToolbox                           0x98b2e1f6 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 411
	10  HIToolbox                           0x98b2e055 SendEventToEventTargetWithOptions + 58
	11  HIToolbox                           0x98b4dc80 SendSimpleWindowEvent + 94
	12  HIToolbox                           0x98b8e390 _ZN10WindowData14SetTitleCommonEPK10__CFString + 114
	13  HIToolbox                           0x98b8e314 SetWindowTitleWithCFString + 52
	14  ???                                 0x13bd15e2 0x0 + 331159010
	15  ???                                 0x13bd1478 0x0 + 331158648
	16  ???                                 0x13bd0600 0x0 + 331154944
	17  ???                                 0x13bd03b8 0x0 + 331154360
	18  ???                                 0x13bcbaff 0x0 + 331135743
	19  ???                                 0x13bcb7c1 0x0 + 331134913
	20  ???                                 0x13bcb576 0x0 + 331134326
	21  ???                                 0x005c9de1 0x0 + 6069729
	22  mono                                0x00010c41 mono_jit_runtime_invoke + 1372
	23  mono                                0x001d0c7a mono_runtime_invoke + 138
	24  mono                                0x001d1c67 mono_runtime_delegate_invoke + 119
	25  mono                                0x002096fc start_wrapper + 682
	26  mono                                0x0024c13d thread_start_routine + 202
	27  mono                                0x00270da4 GC_start_routine + 107
	28  libSystem.B.dylib                   0x9411a81d _pthread_start + 345
	29  libSystem.B.dylib                   0x9411a6a2 thread_start + 34

Debug info from gdb:


=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

Abort trap

Originally Posted by justchat_1

Its an alpha release of something rewritten from the ground up-cut us a little slack.

Was just joking.. sorry if that was misunderstood.