On Sat, Feb 6, 2010 at 12:49 PM, Michael Menegakis <[email protected]> wrote:
>
> 2010/2/6 Dominic Fandrey <[email protected]>
>>
>> In your place I'd give it a run without the VM first:
>>
>> ioquake3 +set vm_ui 0 +set vm_cgame 0 +set vm_game 0
>>
>> If that works we can be certain it's the VM code.
>
> Putting dlls into baseq3 brings up the window, we see the pre-loading screen
> graphic and bang, it goes down right when you expect it to show the loading
> screen with the same bt,
>
> #0  0x000000002b370164 in ?? ()
> #1  0x000000000052eec2 in VM_CallCompiled (vm=0x2034650, args=0x22b070) at
> code/qcommon/vm_x86_64.c:1054
> #2  0x000000000047d34c in VM_Call (vm=0x2034650, callnum=0) at
> code/qcommon/vm.c:790
>
> 1054: __asm__ __volatile__ ( [...........]
>

I don't think you would enter VM_CallCompiled with native DLLs. Maybe
you also need +set sv_pure 0
Refer to the startup log, to see if it contains
Loading vm file vm/ui.qvm...
or
Loading dll file ui.
(and if it is subsequently successful in finding/loading the latter).
_______________________________________________
ioquake3 mailing list
[email protected]
http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org
By sending this message I agree to love ioquake3 and libsdl.

Reply via email to