One frame per second?

seputus · Post by **seputus** » Fri Sep 29, 2006 8:52 pm

I was avoiding mentioning that I have Vista because I didn't want people to give up so early /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" /> ..

But yea.. Vista, RC1 / 5600..

Nvidia Go 6150

DirectX 10

All other DirectX games anddddd OpenGL run fine (I've tried Prey, Doom 3, Fallout, Neverwinter Nights etc.) -- all of which require more demands than Allegiance.

I found that if I use software rendering then it's smooth as silk.. but the textures are crap. But that's what I'll be using in the meantime......

I've forced Vsync off. My desktop is 1280 x 800 - 32-bit.. but I run the game in fullscreen 1024x768 currently (the res/colour depth and window/FS has no effect)

.. i know. wait for the final vista /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />

Dogbones wrote:QUOTE (Dogbones @ Sep 29 2006, 07:43 PM) What operating system?
What specific version of video card?
What version of Direct X?
Have you run the Direct X tests in dxdiag?

I realize other games probably play just fine, but Alleg (even though it uses
DX9 calls now) was set up to run on fairly old system.

What color depth are you running in?
Windowed mode or full screen?
Try 16-bit and full screen, 800x600 or 1024x768

You using an LCD or CRT monitor? I ask because there are options to sync to refresh and if you have a LCD sometimes the refresh info gets 'messed up'.

So while flying everything is extremely jerky?

madpeople · Post by **madpeople** » Fri Sep 29, 2006 9:38 pm

in win xp, the ctrl+alt delete screen says how much cpu a process is using

alt+tab our of alleg and look at the ctrl+alt delete screen, look for anything using 100% cpu (order the list by cpu if nesscarry)

or do what ever is the equivelent is in vista

seputus · Post by **seputus** » Sat Sep 30, 2006 1:32 pm

TaskManager shows that it is Allegiance itself that is sucking all the CPU power. I have a dual core and when I use 3D acceleration it shows 50% usage. The other core isn't being utilized it seems.

beauty · Post by **beauty** » Sun Oct 01, 2006 4:42 am

Only 1 core being used would be normal for a single threaded App (which I think Alleg is).

Has anyone else tried Alleg on Vista?

This could be:
a) Vista driver/XP problem

Vista problem
c) DirectX 10 problem

Right now, I suspect, Direct X 10 making different calls. Have you tried the Beta code? Wait for someone else to speak up, but I think the current Beta code is using some DirectX 8 calls rather than the old DirectX5(?) calls.

ImmortalZ · Post by **ImmortalZ** » Sun Oct 01, 2006 6:06 am

I remember Pook (?) posting a screenshot of Alleg working in Vista.

vlad13 · Post by **vlad13** » Sun Oct 01, 2006 11:35 am

I just tried allegiance in vista and it works fine. I only tried training since it is not installed in vista and asgs gives me an error. I dont even have the sound problems i usually have in xp. Video card radeon 9250 . Standard microsoft drivers. AMD 3500 processor 512 ram Vista beta 2 5384.

Update i installed alleg properly and it works fine online. The only thing is when installing it asks u for dot net 1.1 and when u install dot net 1.1 vista gives u a big warning about how it is not compatible with it. But it still works once u install it.

madpeople · Post by **madpeople** » Sun Oct 01, 2006 1:42 pm

seputus wrote:QUOTE (seputus @ Sep 30 2006, 02:32 PM) TaskManager shows that it is Allegiance itself that is sucking all the CPU power. I have a dual core and when I use 3D acceleration it shows 50% usage. The other core isn't being utilized it seems.

alleg may be starting funny then

when i start alleg directly or by using a link, it works fine. but when i start it from "run" to use the -multi tag, an instance of alleg starts, but the game its self does not come up on screen, i only know its running because task manager says it's process exists, ands that process is using 50% of the cpu. (i used to be able to launch it from run, but not recently. wehther it is faz or a driver update or something)

try launching allegiance directly and doing the training missions, does it then use 50% cpu?
try launching it from run and then do the training, does it use 50% cpu

post results

for normal alleg, it may be how asgs is starting alleg that is causing the problem, or rather, allegiance.exe likes to be started in a certain manner on different systems.

beauty · Post by **beauty** » Sun Oct 01, 2006 6:05 pm

Oh yeah ... Did you download .Net v1.1 off the Microsoft site? That is still required to play and I am sure it isn't included in the normal install.

I am betting that is the problem ...

.Net1.1 will probalby be an option componenet through WindowsUpdate OR you may need to download the package directly off of the Microsoft site.
http://www.microsoft.com/downloads/details...;displaylang=en

Post by **Raveen** » Mon Oct 02, 2006 7:55 am

I doubt it's .NET as that is required for ASGS, not Alleg itself. If you're getting in game then you have .NET.

Have you tried toggling the "Use Secondary Device" (or whatever it is) in the graphics options menu?

Failing that have a look at your settings in DXDiag and see if there are any issues there.

Edit: Alleg is a notorious CPU hog and 100% (or 50% in your case) CPU usage is nothing unusual.

Next · Post by **Next** » Mon Oct 02, 2006 8:18 am

I would guess the problem is DirectX10. Does anyone else here have Vista with 10? As far as I know 10 is no longer backwards compatible with the other versions. It is supposed to "emulate" them but maybe it's not working so well with Allegiance or older games. Have you tried any other games from around 2000-2001? Hopefully DirectX10 is not the issue though or MS fixes it before release.

If not that then I'd say the drivers for your graphics card just aren't working smoothly in Vista yet.