Martin Schweiger's Orbiter simulator: Archives -- December 2002

Number 111 of 195 messages in this Archive
[Date Prev] Main Index [Date Next]
[Thread Prev] Thread Index [Thread Next]

R: Problems with win2k



I got more or less the same errors for the same problem. I noticed that many
.scn files have sections of BEGIN_* and END_* empty. Removing those
declarations increases the percentage of working scenarios. Is it useful?
Roberto

> -----Messaggio originale-----
> Da: Philip Hanson [mailto:grayman3@flashmail.com]
> Inviato: mercoledì 11 dicembre 2002 15.04
> A: orbiter@firedrake.org
> Oggetto: Re: Problems with win2k
>
>
> Strangely enough, I didn't get any memory dump errors until I updated the
> drivers! Now none of the scenarios work - I get an error something like
> 'Rendering with a hardware device failed. Try again with a
> software device.'
> Of course, if I try to switch over to RGB Emu, the Launchpad freezes.
> There's definitely something out of kilter here.
>
> Back when some of the scenarios would work, Orbiter only crashed when I
> selected a .scn file that used the new features, notably when the space
> stations are declared as ships. Very strange.
>
> P.S. Sorry about those read-receipts - I've turned them off so
> there aren't
> 20 replies clogging up the list.
>
> ----- Original Message -----
> From: Orbital Mods
> To: orbiter@firedrake.org
> Sent: Tuesday, December 10, 2002 1:43 PM
> Subject: Re: Problems with win2k
>
>
> I'm glad it worked, I had the same problems myself but now they
> are gone. I
> suspect this problem will be fixed in no time, so keep an eye at new
> Detonator releases. Regarding users with Voodoo problems, there is a good
> chance you can get good results updating your drivers, but be warned, ever
> since 3dfx went out of business there's no support for new drivers, I
> believe. You can find the latest official available ones at
> http://www.voodoofiles.com and then some third party (ie unofficial) ones.
> Take these last ones with a bit of caution and please share your
> results if
> you manage to sort out these problems. Once more let me emphasize this
> matter, uninstalling DirectX will most likely not fix your current issues
> and you're risking your pooter going "out of order". This is
> specially true
> in XP systems so unless you know what you're doing, do not even try doing
> so.
>
> Regards,
> McDope
> ----- Original Message -----
> From: Jon Watkins
> To: orbiter@firedrake.org
> Sent: Tuesday, December 10, 2002 6:32 PM
> Subject: RE: Problems with win2k
>
>
> Yep McDope, that did the trick.  Well blast the darn Anti-Aliasing Switch!
> Thank you very much.  A very happy space camper.  Thank you to all who
> replied to my cry for help.  Still got the Memory Dump errors
> when I select
> some of the scenarios tho L  Oh well one outa two aint bad.  Thanks once
> again.
>
> Jon.
> UK
>
>
>
> --
> Orbiter discussion list:
> - mail orbiter-request@firedrake.org with subject "unsubscribe" to leave
>   or ask the listmaster (@firedrake.org)
> - archives at http://lists.firedrake.org/orbiter/
>


--
Orbiter discussion list:
- mail orbiter-request@firedrake.org with subject "unsubscribe" to leave
  or ask the listmaster (@firedrake.org)
- archives at http://lists.firedrake.org/orbiter/





  • Prev by Date: Re: Problems with win2k
  • Next by Date: Orbiter SDK . . . Compiling .DLLs

  • Previous by thread: Re: Problems with win2k
  • Next by thread: Re: R: Problems with win2k

  • Main Index | Thread Index | Author Index | Archive Index

    roger@nospam.firedrake.org
    Generated: Tue Dec 24 02:08:27 GMT 2002