Author Topic: Series of issues (Windows 8)  (Read 3040 times)

0 Members and 1 Guest are viewing this topic.

Series of issues (Windows 8)
So I'll start off by saying I really don't have a damn clue what I'm doing. I read the guides and instructions and the installation went perfectly the first time, but I accidentally let a windows update go through which absolutely ruined this laptop's performance. I did a system restore afterwards and tried to reinstall everything, and nothing has worked right.

I was able to bring up the launcher, and tried running fs2_open_3_7_0 with the 2014 MediaVPs with no success. Though running the game without the mods runs perfectly well.
As I boot the launcher/game, a few things pop-up: At launcher startup: Failed EnumAdapterModes in UpdateAntialiasList.  Any time I try to change the mods I'd like to use, this pops up: Failed to set graphic mode
Running with fs2_open_3_7_0, I can hear the opening cutscene, but keeps me at the desktop. Everytime I try to switch to FS2, it just puts me back at the desktop.

Any help would be incredibly appreciated. Thanks in advance!

(I did attach the debug log to this post. I think)

[attachment kidnapped by pirates]

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Series of issues (Windows 8)
fs2_open_3_7_0 with the 2014 MediaVPs
The 2014 MediaVPs require a newer version of FSO. Try 3.7.2 RC4.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 
Re: Series of issues (Windows 8)
fs2_open_3_7_0 with the 2014 MediaVPs
The 2014 MediaVPs require a newer version of FSO. Try 3.7.2 RC4.

Mmk well that solves part of the problem. Though now, the resolution isn't correct, and the same two pop-ups still show up, meaning I can't actually change the resolution before launching the game. The dropdown menu is just blank.

 

Offline Parias

  • 27
Re: Series of issues (Windows 8)
A friend running Windows 8 and playing FS2 at a LAN party literally just ran into this very same problem today.

Run the launcher as admin, and use Windows Vista / 7 / whatever compatibility mode. Should fix it.

 
Re: Series of issues (Windows 8)
A friend running Windows 8 and playing FS2 at a LAN party literally just ran into this very same problem today.

Run the launcher as admin, and use Windows Vista / 7 / whatever compatibility mode. Should fix it.

Sweet. Still getting some of the same pop-ups, but it looks like the resolution is fixed. Thanks!

But I don't think I should still be getting these pop-ups.

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Series of issues (Windows 8)
But I don't think I should still be getting these pop-ups.
And what are "these pop-ups"?
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 
Re: Series of issues (Windows 8)
I recently installed on Windows 8. I was getting the same problem pop ups:

"Failed EnumAdapterModes in UpdateAntialiasList"

"Failed to Set Graphics Mode"

It was because I needed to run install and run from the wxlauncher and then update my video card driver.

Not sure if you tried either of these fixes.


 
Re: Series of issues (Windows 8)
It was because I needed to run install and run from the wxlauncher and then update my video card driver.

Not sure if you tried either of these fixes.

Could you be a little clearer here? I know my video card is up to date, but I don't exactly know what you mean by "run install and run from the wxlauncher" (is wxlauncher the one given to us during the FSO installation? or some different launcher?

 

Online Cyborg17

  • 29
  • A-1 Supar
Re: Series of issues (Windows 8)
The WxLauncher is not given by the installer because it has a separate installer.  Installer 5.5g comes with the FSO installer.

 
Re: Series of issues (Windows 8)
Camelpockets, did you get the wxlauncher figured out? Windows 8 can't run the launcher set up during the FSO install.

Go to link below and install mxlauncher into your Freespace folder. Once you're done, you'll find a mxlauncher folder, open it, open the bin folder and you will find the launcher you need to run the game in Windows 8.

All this is based on my experience getting it on my Windows 8 laptop a few days ago. Hope it helps.

http://code.google.com/p/wxlauncher/downloads/list?can=3

 

Offline pecenipicek

  • Roast Chicken
  • 211
  • Powered by copious amounts of coffee and nicotine
    • Minecraft
    • Skype
    • Steam
    • Twitter
    • PeceniPicek's own deviantart page
Re: Series of issues (Windows 8)
Camelpockets, did you get the wxlauncher figured out? Windows 8 can't run the launcher set up during the FSO install.

Go to link below and install mxlauncher into your Freespace folder. Once you're done, you'll find a mxlauncher folder, open it, open the bin folder and you will find the launcher you need to run the game in Windows 8.

All this is based on my experience getting it on my Windows 8 laptop a few days ago. Hope it helps.

http://code.google.com/p/wxlauncher/downloads/list?can=3
do not under any circumstances install it in the fso folder. wxLauncher goes in its own folder.

also, add -no_glsl to your command line options. We are sorry, your graphics card is bad and there is not much else that can be done about that.
Skype: vrganjko
Ho, ho, ho, to the bottle I go
to heal my heart and drown my woe!
Rain may fall and wind may blow,
and many miles be still to go,
but under a tall tree I will lie!

The Apocalypse Project needs YOU! - recruiting info thread.

 
Re: Series of issues (Windows 8)
Camelpockets, did you get the wxlauncher figured out? Windows 8 can't run the launcher set up during the FSO install.

Go to link below and install mxlauncher into your Freespace folder. Once you're done, you'll find a mxlauncher folder, open it, open the bin folder and you will find the launcher you need to run the game in Windows 8.

All this is based on my experience getting it on my Windows 8 laptop a few days ago. Hope it helps.

http://code.google.com/p/wxlauncher/downloads/list?can=3

Yup, the wxlauncher is working fine now. Took a little while to figure it out, but it's running. Thanks folks!

Quote
also, add -no_glsl to your command line options. We are sorry, your graphics card is bad and there is not much else that can be done about that.

I knew that the mediavps graphics ramp-ups were pretty intense, but I didn't realize how good a system needed to be to run it with everything maxxed. But graphics are just meh. As long as I can shoot straight I'm cool. I'll just take a peek at a few screenshots to admire the beauty.
« Last Edit: September 04, 2014, 01:56:10 pm by camelpockets »

 

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: Series of issues (Windows 8)
Camelpockets, you only have one graphics card in device manager, right?

 
Re: Series of issues (Windows 8)
Camelpockets, you only have one graphics card in device manager, right?

Si senor.

Correction: Actually I have two, the Nvidia GeForce GTX 870m and the Intel(R) HD Graphics 4600.
« Last Edit: September 05, 2014, 12:41:39 pm by camelpockets »

 
Re: Series of issues (Windows 8)
Camelpockets, you only have one graphics card in device manager, right?

Actually I have two, the Nvidia GeForce GTX 870m and the Intel(R) HD Graphics 4600.

 

Offline jr2

  • The Mail Man
  • 212
  • It's prounounced jayartoo 0x6A7232
    • Steam
Re: Series of issues (Windows 8)
Thank you for the answer, I'll try this as soon as I get back from work.

By the way, I am on an NVida Optimus powered laptop (i.e. I have two graphic cards, an HD Intel Graphics and an NVidia chipset), so it that's the problem does it mean that the game is not using the NVidia card? Is there any configuration I need to provide to switch that on?

Thank you again anyway!
It's in the nvidia control panel, add the FSO exe to the profiles and tell it to use the nvidia. Not very specific, I know, it's been a while.

However, with mine, that setting seems to be ignored last time I tried. It's only FSO and a few other old games  that ignore this.

Here let me fire up my laptop and show you.


EDIT: (using my wife's laptop cause it's closer lol -- same setup though)


OK, with @DahBlount setting changes I could get past the opening sequence. I also tried configuring the system in order to use the NVidia graphic card but it didn't work, so I can only play disabling those options.

I'll have a look into this, but for now many thanks!  ;)
Err..  Had to dig for this :


Could you try an antipodes build? The OpenGL context is created by SDL which might be different from what FSO currently does.

I never tried that as I only just got my laptop running.   Try it and see if it uses nvidia.

 
Re: Series of issues (Windows 8)
Yup I just saw that. I was trying to run Star Citizen earlier today, and couldn't figure out why I couldn't run it at all. Apparently that's why.