Comments

cinder1992 · #1

20/6/12: I will be updating this tutorial in a few days... after 2 years. WINE has changed, and the tutorial will be updated accordingly..

well, that is if I can get linux to install.

Took me a while, but I got it working.

HOW TO RUN ORBITER 2010 IN LINUX:

To start, you need a copy of wine, in ubuntu and some distrobutions, you can get it off the package manager, in Arch Linux, use pacman to get it:

Code:

pacman -S wine

otherwise, get it off of the Wine HQ website.

Next (sorry for borrowing this, but it WORKS.), you need to get winetricks. a simple process, just use the command here:

Code:

wget http://www.kegel.com/wine/winetricks

after you have that, you need cabextract, a simple tool that will allow you to use winetricks to it's fullest. some distros have this built-in, but I'm going to include the command, just in case.

Code:

ARCH LINUX: pacman -S cabextract
DEBIABN/UBUNTU: apt-get install cabextract

you need to run wine once in order for it to auto-config, the easyest thing to do is to open notepad. use this command:

Code:

wine notepad

it should atoconfig and open notepad, colse notepad, we do not need it.

you now need to get a copy of orbiter 2010, the ZIP version, I don't think the MSI one works. place the .zip file in your home directory and use this command to unzip it:

Code:

unzip ~/orbiter100606.zip "~/.wine/drive_c/Orbiter/"

There! orbiter is technicly installed, you just have to do the final steps...

you now need to install the VC++ 2005 runtime, do this by using this set of commands:

Code:

cd ~/
sh winetricks vcrun2005

follow the instructions on the window that pops up, the runtime shuld now be installed.

now, the final step. Orbiter 2010's program checker dosn't like the wine DirectX, so you need to override the check, this can be done by moving the real executible to the current one's place. use the following commands:

Code:

cp "~/.wine/drive_c/Orbiter/Install/orbiter.bin" "~/.wine/drive_c/Orbiter/orbiter.exe"

you need to say yes to the overwrite. This will override the check, but you MUST NOT RUN THE CHECK. It screws up wine.

Now launch orbiter using:

Code:

wine orbiter
(if that command didn't work, you need to change to your orbiter directiory using the following command.)
cd "~/.wine/drive_c/Orbiter"

And happy orbiting

INTRESTING GLITCH: the text is upside down.

REQUIRED FOR DECENT FRAMERATES:
It helps to have OGLA installed, get the latest install of OGLA from here at Orbiter-forum and extract it to any old directory

Code:

unzip ~/oglaclient-VERSION_HERE ~/OGLA.TEMP

navigate to the OGLA directory you just made and make the following corrections
note, it is entirely possible that this fault will be fixed, I will update the tutorial when this occurs.

Code:

cd OGLA.TEMP
cp modules Modules
cp config Config
rm config
cd Modules
cp plugins Plugins
rm plugins

This will correct a minor fault

you now need to move the temporary dir to the install of orbiter, this can be achieved with the use of these commands

Code:

cd ~/
cp OGLA.TEMP ~/.wine/drive_c/Orbiter
rm OGLA.TEMP

just run the orbiter server

Code:

cd ~/.wine/drive_c/Orbiter
wine orbiter_ng

you also need a copy of these three fonts or OGLA will have a hissy-fit:

Code:

cour.ttf
arial.ttf
times.ttf

If you have a windows install, go crazy and just move the entire contents of the windows fonts directory into this directory:

Code:

~/.wine/c_drive/windows/fonts

I recommend doing this as many addons may use other fonts, and if those fonts aren't present, well... yeah.

and happy orbiting

**eveningsky339** · 06-17-2010, 03:44 PM

Code:

DEBIABN/UBUNTU: app-get install cabextract

The bolded command is a typo. It should be apt. Not a big deal, one would expect a Ubuntu/Debian user to recognize this.

I am downloading Orbiter 2010 onto my Ubuntu machine. I will post my results shortly.

EDIT: First try was... interesting. When I selected "Intro to Orbiter" some sort of pseudo-screenshot was burned into the window and a crash to desktop occurred. Fond memories of Windows Vista...

cinder1992 · 06-17-2010, 05:36 PM

fixed the typo, I also noticed that the thing was as slow as a microbe on a slug, try orbiter_ng with the OLGA client (NOTE: this has NEVER been tested, even I'm afraid to try <_<)

**eveningsky339** · 06-17-2010, 06:02 PM

Quote:

Originally Posted by cinder1992

fixed the typo, I also noticed that the thing was as slow as a microbe on a slug, try orbiter_ng with the OLGA client (NOTE: this has NEVER been tested, even I'm afraid to try <_<)

I may just give it a go... Any further attempts to start Orbiter under wine result in a frozen screen and some sort of lecture on hexadecimal binary code in the command terminal.

EDIT: Wine does not like the Orbiter_ng.exe, even after I marked it as executable. Any way to get this beauty up and running?

cinder1992 · 06-17-2010, 07:38 PM

can you post a copy of that "lecture"? It may help me to "debug" the tutorial.

**eveningsky339** · 06-17-2010, 11:34 PM

Here's the command I used to launch Orbiter, for what it's worth.

Code:

eric@eric-laptop:~/.wine/drive_c/Orbiter$ wine orbiter

And here's what pops up in the command terminal (Orbiter window is completely white, "encountered an error and has to close" box pops up).

Code:

fixme:ddraw:DirectDrawEnumerateExA flags 0x00000007 not handled
fixme:win:EnumDisplayDevicesW ((null),0,0xaef04c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0xaee3d0,0x00000000), stub!
fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
fixme:d3d7:IDirect3DVertexBufferImpl_Optimize (0x1d0050)->(0x15f0d8,00000000): stub!
err:ddraw:PixelFormat_WineD3DtoDD Can't translate this Pixelformat 58
err:ddraw:PixelFormat_WineD3DtoDD Can't translate this Pixelformat 64
err:d3d_surface:read_from_framebuffer_texture >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500) from glReadBuffer @ surface.c / 1505
err:d3d_surface:read_from_framebuffer_texture >>>>>>>>>>>>>>>>> GL_INVALID_FRAMEBUFFER_OPERATION (0x506) from glCopyTexSubImage2D @ surface.c / 1535
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
err:d3d_surface:read_from_framebuffer >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500) from glReadBuffer @ surface.c / 1277
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
err:ddraw:PixelFormat_WineD3DtoDD Can't translate this Pixelformat 58
err:ddraw:PixelFormat_WineD3DtoDD Can't translate this Pixelformat 64
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
err:ddraw:PixelFormat_WineD3DtoDD Can't translate this Pixelformat 58
err:ddraw:PixelFormat_WineD3DtoDD Can't translate this Pixelformat 64
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
fixme:d3d:context_apply_state Activating for CTXUSAGE_BLIT for an offscreen target with ORM_FBO. This should be avoided.
err:d3d:context_apply_draw_buffer >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawBuffers() @ context.c / 1890
wine: Unhandled page fault on write access to 0x7b1dd000 at address 0x68281d8a (thread 0009), starting debugger...

clickypens · 06-18-2010, 03:14 AM

I got the same thing in Ubuntu 10.04, eveningsky

cinder1992 · 06-18-2010, 10:29 AM

ah. I think you're trying to run in fullscreen, try windowed mode.

If that does not work, try getting a non-wine version of directX from another game, I think that might help.

and if all else fails, get the 1.1.44 version of wine, it could be that your running one of the RC versions, this CAN and WILL cause problems.

and if none of the above work, well, get a lighter version of linux. Ubuntu has been known to conflict with applications running in wine.

**eveningsky339** · 06-18-2010, 11:20 AM

Quote:

Originally Posted by cinder1992

ah. I think you're trying to run in fullscreen, try windowed mode.

If that does not work, try getting a non-wine version of directX from another game, I think that might help.

and if all else fails, get the 1.1.44 version of wine, it could be that your running one of the RC versions, this CAN and WILL cause problems.

and if none of the above work, well, get a lighter version of linux. Ubuntu has been known to conflict with applications running in wine.

I will give all these a shot after work.

I was planning on replacing Ubuntu with another distro in short order, as there are many things I've come to dislike about it. However, I was planning on openSUSE 11.2, which isn't exactly light.

Linguofreak · 06-18-2010, 02:01 PM

One heads up: The capitalizations for "Config" and "Modules" in the Oglaclient and main Orbiter zips are different, and Windows folds case internally. Therefore, while the Oglaclient zip will unzip properly on Windows, it won't on Linux. You will need to merge "config" with "Config" and "modules" with "Modules" for Orbiter_ng to work properly. (It seems that it runs, but exits silently and immediately without throwing an error message if it does not find a client module).

EDIT: Forgot to mention, you also need to merge the "Plugin" folders inside modules.

--------------------------

After some tinkering, I announce my success!!! OGLAClient + Wine Works!!!

Orbit achieved!!! Earlier bugs under wine (keyboard not working after bringing up the menu window with F4), seem to have disappeared. Framerate is in the 100's to 200's. My only complaints are a bit of flickering in the MFD area, MFD glitches (no text displayed, artificial horizon on surface MFD covers the whole of the MFD and speed/altitude/acceleration data isn't displayed), and sore hands from flying the DG on a laptop without a joystick...

A screenie will follow when I get it uploaded.

EDIT: I have discovered that the External MFD module will cause problems.

EDIT: Screenshots!

**Xyon** · 06-18-2010, 03:25 PM

Those are some impressive results... especially the framerates.

Linguofreak · 06-18-2010, 03:39 PM

Indeed. The Windows machine I use at home caps at 60, though I think that has more to do with typical monitor refresh rates being 60 Hz than with performance limitations, given the consistency of the 60 FPS I get and that it doesn't drop from that without really high loads, plus the fact that it's a more powerful machine and running Orbiter natively rather than under a compatibility layer. I am finding I'm getting some kind of crash on exiting, but that doesn't interfere with actual play.

EDIT: More screenies!

This first was actually the first one I took, but I missed it when I made the first upload:

**Xyon** · 06-18-2010, 03:44 PM

My monitor runs at 85Hz and I get 195FPS in Orbiter 2010 on a bad day, 25 at the minimum... I don't see your point about 60Hz. Monitor refresh rate is not the same as framerate as measured in Orbiter.

**dbeachy1** · 06-18-2010, 03:46 PM

Quote:

Originally Posted by Linguofreak

The Windows machine I use at home caps at 60, though I think that has more to do with typical monitor refresh rates being 60 Hz than with performance limitations

If your framerate never exceeds 60, it sounds like Orbiter has vertical sync enabled. If you click "Disable Vertical Sync" in the video tab of the launchpad or run Orbiter in a window it will allow Orbiter to run without a framerate cap.

Linguofreak · 06-18-2010, 04:08 PM

Quote:

Originally Posted by Xyon

My monitor runs at 85Hz and I get 195FPS in Orbiter 2010 on a bad day, 25 at the minimum... I don't see your point about 60Hz. Monitor refresh rate is not the same as framerate as measured in Orbiter.

I think it may be the graphic card running at an assumed monitor refresh rate. I don't know what the monitor itself runs at, it may or may not be 60 Hz. All I know is that Orbiter runs at a consistent and exact 60 Hz, never more, and never less unless under very high load. (And I'm not sure whether or not I've ever loaded it enough to push it below 60 Hz). Everything else is hypotheses.

Quote:

Originally Posted by dbeachy1

If your framerate never exceeds 60, it sounds like Orbiter has vertical sync enabled. If you click "Disable Vertical Sync" in the video tab of the launchpad or run Orbiter in a window it will allow Orbiter to run without a framerate cap.

I think that occured to me and I tried it, without effect, though I'll have to check when I get back to be sure...

06-17-2010, 03:44 PM	#2
eveningsky339 Resident Orbiter Slave	Code: DEBIABN/UBUNTU: app-get install cabextract The bolded command is a typo. It should be apt. Not a big deal, one would expect a Ubuntu/Debian user to recognize this. I am downloading Orbiter 2010 onto my Ubuntu machine. I will post my results shortly. EDIT: First try was... interesting. When I selected "Intro to Orbiter" some sort of pseudo-screenshot was burned into the window and a crash to desktop occurred. Fond memories of Windows Vista... Last edited by eveningsky339; 06-17-2010 at 04:08 PM.

06-17-2010, 06:02 PM	#4
eveningsky339 Resident Orbiter Slave	Quote: Originally Posted by cinder1992 fixed the typo, I also noticed that the thing was as slow as a microbe on a slug, try orbiter_ng with the OLGA client (NOTE: this has NEVER been tested, even I'm afraid to try <_<) I may just give it a go... Any further attempts to start Orbiter under wine result in a frozen screen and some sort of lecture on hexadecimal binary code in the command terminal. EDIT: Wine does not like the Orbiter_ng.exe, even after I marked it as executable. Any way to get this beauty up and running? Last edited by eveningsky339; 06-17-2010 at 06:12 PM.

06-18-2010, 10:29 AM	#8
cinder1992 Random failhurricane.	ah. I think you're trying to run in fullscreen, try windowed mode. If that does not work, try getting a non-wine version of directX from another game, I think that might help. and if all else fails, get the 1.1.44 version of wine, it could be that your running one of the RC versions, this CAN and WILL cause problems. and if none of the above work, well, get a lighter version of linux. Ubuntu has been known to conflict with applications running in wine. Last edited by cinder1992; 06-18-2010 at 10:33 AM.

06-18-2010, 02:01 PM	#10
Linguofreak Orbinaut	One heads up: The capitalizations for "Config" and "Modules" in the Oglaclient and main Orbiter zips are different, and Windows folds case internally. Therefore, while the Oglaclient zip will unzip properly on Windows, it won't on Linux. You will need to merge "config" with "Config" and "modules" with "Modules" for Orbiter_ng to work properly. (It seems that it runs, but exits silently and immediately without throwing an error message if it does not find a client module). EDIT: Forgot to mention, you also need to merge the "Plugin" folders inside modules. -------------------------- After some tinkering, I announce my success!!! OGLAClient + Wine Works!!! Orbit achieved!!! Earlier bugs under wine (keyboard not working after bringing up the menu window with F4), seem to have disappeared. Framerate is in the 100's to 200's. My only complaints are a bit of flickering in the MFD area, MFD glitches (no text displayed, artificial horizon on surface MFD covers the whole of the MFD and speed/altitude/acceleration data isn't displayed), and sore hands from flying the DG on a laptop without a joystick... A screenie will follow when I get it uploaded. EDIT: I have discovered that the External MFD module will cause problems. EDIT: Screenshots! Last edited by Linguofreak; 06-18-2010 at 03:21 PM.

06-18-2010, 03:39 PM	#12
Linguofreak Orbinaut	Indeed. The Windows machine I use at home caps at 60, though I think that has more to do with typical monitor refresh rates being 60 Hz than with performance limitations, given the consistency of the 60 FPS I get and that it doesn't drop from that without really high loads, plus the fact that it's a more powerful machine and running Orbiter natively rather than under a compatibility layer. I am finding I'm getting some kind of crash on exiting, but that doesn't interfere with actual play. EDIT: More screenies! This first was actually the first one I took, but I missed it when I made the first upload: Last edited by Linguofreak; 06-18-2010 at 03:59 PM.

06-17-2010, 05:36 PM	#3
cinder1992 Random failhurricane.	fixed the typo, I also noticed that the thing was as slow as a microbe on a slug, try orbiter_ng with the OLGA client (NOTE: this has NEVER been tested, even I'm afraid to try <_<)

06-17-2010, 07:38 PM	#5
cinder1992 Random failhurricane.	can you post a copy of that "lecture"? It may help me to "debug" the tutorial.

06-18-2010, 03:14 AM	#7
clickypens Orbinauta	I got the same thing in Ubuntu 10.04, eveningsky

06-18-2010, 11:20 AM	#9
eveningsky339 Resident Orbiter Slave	Quote: Originally Posted by cinder1992 ah. I think you're trying to run in fullscreen, try windowed mode. If that does not work, try getting a non-wine version of directX from another game, I think that might help. and if all else fails, get the 1.1.44 version of wine, it could be that your running one of the RC versions, this CAN and WILL cause problems. and if none of the above work, well, get a lighter version of linux. Ubuntu has been known to conflict with applications running in wine. I will give all these a shot after work. I was planning on replacing Ubuntu with another distro in short order, as there are many things I've come to dislike about it. However, I was planning on openSUSE 11.2, which isn't exactly light.

06-18-2010, 03:25 PM	#11
Xyon Error 418: I'm a teapot	Those are some impressive results... especially the framerates.

06-18-2010, 03:44 PM	#13
Xyon Error 418: I'm a teapot	My monitor runs at 85Hz and I get 195FPS in Orbiter 2010 on a bad day, 25 at the minimum... I don't see your point about 60Hz. Monitor refresh rate is not the same as framerate as measured in Orbiter.

06-18-2010, 03:46 PM	#14
dbeachy1 O-F Administrator	Quote: Originally Posted by Linguofreak The Windows machine I use at home caps at 60, though I think that has more to do with typical monitor refresh rates being 60 Hz than with performance limitations If your framerate never exceeds 60, it sounds like Orbiter has vertical sync enabled. If you click "Disable Vertical Sync" in the video tab of the launchpad or run Orbiter in a window it will allow Orbiter to run without a framerate cap.

06-18-2010, 04:08 PM	#15
Linguofreak Orbinaut	Quote: Originally Posted by Xyon My monitor runs at 85Hz and I get 195FPS in Orbiter 2010 on a bad day, 25 at the minimum... I don't see your point about 60Hz. Monitor refresh rate is not the same as framerate as measured in Orbiter. I think it may be the graphic card running at an assumed monitor refresh rate. I don't know what the monitor itself runs at, it may or may not be 60 Hz. All I know is that Orbiter runs at a consistent and exact 60 Hz, never more, and never less unless under very high load. (And I'm not sure whether or not I've ever loaded it enough to push it below 60 Hz). Everything else is hypotheses. Quote: Originally Posted by dbeachy1 If your framerate never exceeds 60, it sounds like Orbiter has vertical sync enabled. If you click "Disable Vertical Sync" in the video tab of the launchpad or run Orbiter in a window it will allow Orbiter to run without a framerate cap. I think that occured to me and I tried it, without effect, though I'll have to check when I get back to be sure...

Quick Links	Need Help?
About Us Register to Participate Orbiter Website Orbiter Download Projects Recommended Addons Orbit Hangar Mods Photo Gallery Social Groups External Links	Did you forget your password? Rules & Guidelines Frequently Asked Questions Orbiter F.A.Q. Orbiter Tutorials Orbiter IRC Chat Search Forum Site Map Contact Us Mark Forums Read