For the Win8 users...

JonathanBleeker
Posts: 3446
Joined: Sat Mar 13, 2010 7:38 pm
For the Win8 users...

Post by JonathanBleeker » Tue Dec 30, 2014 12:59 pm

Try this please

http://www.orbxsystems.com/forum/topic/ ... ntry816027
Funny, I'm been flying in Windows 8.1 since it came out. The trick it to install it in Windows 7/ Admin mode. before executing the installation. works fine. :) Also go into "turn on windows feature on or Off" and put a check in the box for .NET3.5 Framework{ including 2.0 and 3.0} before installing the package on Windows 8.1

Nullack
Posts: 6
Joined: Sun Feb 08, 2015 12:36 am
Re: For the Win8 users...

Post by Nullack » Sun Feb 08, 2015 10:53 am

Ok Ill give it a try. Im on 64 bit Windows 8.1

I didnt see the fine print saying Windows 8.x not supported when I bought this from the flight sim web store right down the bottom of the product page.

Gee guys, you know there is tens of millions of Windows 8.X licences out there, your going to have to support Windows 8.x at some point in time, whats the problem? The licence doesnt cost much and I'd think you would not want to not alienate Windows 8.x users? Why cant you run a testbed of machines from Vista onwards, and take part in the dev previews of things like windows 10? Why do this to yourselves by restricting sales, or in my case have customers who didnt know and then become frustrated.

I'll try to help you guys as much as I can on my end - surely you want to make the product Win8.x compatible and supported?

When I bought the product, the fligh sim store provided download to v2.141208. What exactly is the current build version released to production for P3DV2? This is another issue, to be constructive and help you guys out, why cant I find a clear sticky thread saying, for P3DV2, this is the current released build number?

Im finding when I go into the P3dV2 app, I select the Milviz Helo, I hear the engine kinda start to die then I get a crash with P3D erroring out to the desktop

In the app error log, I get these sorts of entries

Code: Select all

Log Name:      Application
Source:        Application Error
Date:          8/02/2015 9:36:38 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Bismarck
Description:
Faulting application name: Prepar3D.exe, version: 2.4.11570.0, time stamp: 0x542314d3
Faulting module name: MSVCR90.dll, version: 9.0.30729.8387, time stamp: 0x51ea24a5
Exception code: 0xc0000417
Fault offset: 0x00031484
Faulting process ID: 0x2748
Faulting application start time: 0x01d0438aea0003a0
Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCR90.dll
Report ID: 5c62b3d3-af7e-11e4-beb0-5404a6f2d06a
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-08T10:36:38.000000000Z" />
    <EventRecordID>44288</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Bismarck</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>2.4.11570.0</Data>
    <Data>542314d3</Data>
    <Data>MSVCR90.dll</Data>
    <Data>9.0.30729.8387</Data>
    <Data>51ea24a5</Data>
    <Data>c0000417</Data>
    <Data>00031484</Data>
    <Data>2748</Data>
    <Data>01d0438aea0003a0</Data>
    <Data>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe</Data>
    <Data>C:\WINDOWS\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCR90.dll</Data>
    <Data>5c62b3d3-af7e-11e4-beb0-5404a6f2d06a</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Code: Select all

Log Name:      Application
Source:        Windows Error Reporting
Date:          8/02/2015 9:36:43 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Bismarck
Description:
Fault bucket 81794939566, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 2.4.11570.0
P3: 542314d3
P4: MSVCR90.dll
P5: 9.0.30729.8387
P6: 51ea24a5
P7: 00031484
P8: c0000417
P9: 00000000
P10: 

Attached files:
C:\Users\xxxx\AppData\Local\Temp\WERE665.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\xxxx\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_f4dfa25aabdd8f7e735911fc3b50f0e15da4eb6f_7a908078_039df6b1

Analysis symbol: 
Rechecking for solution: 0
Report ID: 5c62b3d3-af7e-11e4-beb0-5404a6f2d06a
Report Status: 0
Hashed bucket: c3c0e5d09e36d9761c86ad4bd6cc0927
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-08T10:36:43.000000000Z" />
    <EventRecordID>44289</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Bismarck</Computer>
    <Security />
  </System>
  <EventData>
    <Data>81794939566</Data>
    <Data>5</Data>
    <Data>BEX</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>Prepar3D.exe</Data>
    <Data>2.4.11570.0</Data>
    <Data>542314d3</Data>
    <Data>MSVCR90.dll</Data>
    <Data>9.0.30729.8387</Data>
    <Data>51ea24a5</Data>
    <Data>00031484</Data>
    <Data>c0000417</Data>
    <Data>00000000</Data>
    <Data>
    </Data>
    <Data>
C:\Users\xxxx\AppData\Local\Temp\WERE665.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\Users\xxxx\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_f4dfa25aabdd8f7e735911fc3b50f0e15da4eb6f_7a908078_039df6b1</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>5c62b3d3-af7e-11e4-beb0-5404a6f2d06a</Data>
    <Data>0</Data>
    <Data>c3c0e5d09e36d9761c86ad4bd6cc0927</Data>
  </EventData>
</Event>

spirit_66
Posts: 8
Joined: Mon Mar 10, 2014 2:21 am
Location: Chiang Mai/Thailand
Re: For the Win8 users...

Post by spirit_66 » Sun Feb 08, 2015 2:54 pm

I wonder why these problems with Windows 8.1 exist. I never had any and now it works in Windows 10 too very well.
Spirit

PS: I never do this!!! C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe

Nullack
Posts: 6
Joined: Sun Feb 08, 2015 12:36 am
Re: For the Win8 users...

Post by Nullack » Mon Feb 09, 2015 7:48 am

Ok Jonthan, to report back as I promised about trying the quote you made in your first post

Before I start, let me just say please I mean what I say when I say I'll help you. This is because I love Milviz. This is because as a Windows 8.x user, I dont want to be excluded from the joy of being a customer. I dont want Milviz to say I cant be in the club. That wont happen. And my wife knows very well how stubborn I am, I will, and you will see, spend hours and hours helping you. Because its not only my word, but my heart. Flight Simming is my peace and sanity and therapy I need in my life. Why should my flight simming be without Milviz? Do you hear me?

It also helps I am a windows internals expert, an ICT professional, I know more about windows than the majority of others and thats not a baseless brag, its true

Ok *THE CRASHING IS FIXED*

What I did is

Uninstall
Set the windows compatability for windows seven on the binary installer, including the extra step of setting for all users too just cos Im a belts and bracers tech guy
Executed the installer
Answered all install prompts to install onto windows 8.1 with P3DV2
The installer exited runtime normally
I then manually deleted the milviz files in the MD helo directory and pasted my add on key into the same directory
I then set the windows compatability for windows seven on the shortcut to the MM, including the extra step of setting for all users too
I then in windows explorer went into the MD helo directory, and set the windows compatability for windows seven on the shortcut to the MV_ACM.exe, including the extra step of setting for all users too

Then it all worked, no more crashing, or atleast in a 30 minute test run

More testing to come

I need you please to sort out release management. I want clear and concise user based instructions on the current P3DV2 production version there is available, and how to get it. It should just be simple, like what A2A simulations do, for users to manage patches and have certainty over release management on their systems

If you want, I can send you my resume. I've got twenty years in IV&V, V&V, including to the programme test manager level. But to me my resume is a bit of paper, what I do and say is my value. Are you ready for me to help? What will you do, to make sure that everyone on modern windows is ready to love milviz too? hmm?

FireRx
Posts: 99
Joined: Sat Jul 12, 2014 5:50 am
Re: For the Win8 users...

Post by FireRx » Wed Mar 18, 2015 3:34 pm

FYI,
Aircraft works excellent on Windows 10 also. :D

N4GIX
Posts: 1023
Joined: Mon Sep 06, 2010 3:47 pm
Re: For the Win8 users...

Post by N4GIX » Wed Mar 18, 2015 4:10 pm

Nullack wrote:Gee guys, you know there is tens of millions of Windows 8.X licences out there, your going to have to support Windows 8.x at some point in time, whats the problem? The licence doesnt cost much and I'd think you would not want to not alienate Windows 8.x users? Why cant you run a testbed of machines from Vista onwards, and take part in the dev previews of things like windows 10? Why do this to yourselves by restricting sales, or in my case have customers who didnt know and then become frustrated.
Okay, the first is quite a bit of hyperbole, but the point is taken: there are a lot of simmers using Win 8.x for various reasons. The reality is that there most likely aren't even as many as a fifty-thousand folks using FSX or P3D. :)

Of the answers to the various "Whys" you've posed however, the first and major reason is cost. We are a group of folks who work together in a common endeavor, but are scattered across at least three major continents, many time zones and as many as eight or nine countries. We communicate via email, private forums, Skype and the very occasional cell pnone call.

Were we all working out of the same office space it would probably be feasible to have multiple test systems running myriad different components and operating systems. As it is however some of us are fortunate to have one computer system from which to work. Of all the team members I may well be the only one with a multi-system LAN available to me, at that's only because I'm a pack-rat. Every time I replace a computer, if the one being replaced still has any life left in it at all, I move it "down the LAN" and use it for testing and evaluation of work in progress.

I am delighted that you have invested the time and effort to get things running on your system, and for sharing your findings and expertise with everyone. Hopefully this will assist others in overcoming the various pecularities and "gottchas" that Microsoft has bundled in their latest incarnation of WinME known as Win8.x. Even they are implicitly acknowledging this less than stellar OS by their determination to offer everyone a free upgrade to Win10.x in the near future.

Oh joy... then we can 'enjoy' going through all this again. :?

JonathanBleeker
Posts: 3446
Joined: Sat Mar 13, 2010 7:38 pm
Re: For the Win8 users...

Post by JonathanBleeker » Wed Mar 18, 2015 5:06 pm

FWIW I do have a win8 drive now....But its not quite up to speed yet as I got a large string of priorities to move down and its somewhere there...

Krazycolin
Site Admin
Posts: 1728
Joined: Mon Sep 08, 2008 4:18 pm
Re: For the Win8 users...

Post by Krazycolin » Wed Mar 18, 2015 7:09 pm

Well, it's a good thing that I get to decide...

For now, and for the forseeable future, Win 8 + will NOT be supported until such time that there is at least 1/4 of our beta team has it installed. None do at this time so, though there may well be many out there, I can count the ones I know who are simmers on my hands and feet.

I get that you might want to be at the cutting edge but in this "game" tried and trusted is the way to go (for us at least).

Thanks.

However, I should and DO thank you for your help... if other users who have win8 run into issues, I will send them here...

cyberdal
Posts: 4
Joined: Tue Nov 25, 2014 2:20 am
Re: For the Win8 users...

Post by cyberdal » Thu Mar 19, 2015 6:36 pm

When I purchased the MD530 I installed it into P3D v2.4 on Win 8.1 and it worked just fine. I purchased the addon package and it installed just fine. I could use the MM manager and modify everything. No CTD and it flew flawless. I then updated P3D to v2.5 with a total uninstall and reinstall of everything. Using the MD530 v2.150210 I installed as usual. However, the MM manager will not modify anything and all liveries have the same no doors, no pilot, etc. setup. It still flies normal and no CTD. I uninstalled and reinstalled using the above procedures and still cannot get the MM manager to work. I have read and understand the no Win 8.1 support by MilViz so I am hoping for any additional suggestions from others who read this forum. Thank you.

N4GIX
Posts: 1023
Joined: Mon Sep 06, 2010 3:47 pm
Re: For the Win8 users...

Post by N4GIX » Thu Mar 19, 2015 10:09 pm

Since the Milviz Menu Manager runs independent of FSX and/or P3D, changing from v2.4 to v2.5 really should have nothing to do with whether it works or not.

cyberdal
Posts: 4
Joined: Tue Nov 25, 2014 2:20 am
Re: For the Win8 users...

Post by cyberdal » Fri Mar 20, 2015 3:02 am

N4GIX wrote:Since the Milviz Menu Manager runs independent of FSX and/or P3D, changing from v2.4 to v2.5 really should have nothing to do with whether it works or not.
Yes. I only mention that for troubleshooting ideas.

JonathanBleeker
Posts: 3446
Joined: Sat Mar 13, 2010 7:38 pm
Re: For the Win8 users...

Post by JonathanBleeker » Fri Mar 20, 2015 7:29 am

If you right click on the menu manager shortcut and check what path it points to, where does it go?

cyberdal
Posts: 4
Joined: Tue Nov 25, 2014 2:20 am
Re: For the Win8 users...

Post by cyberdal » Fri Mar 20, 2015 4:30 pm

JonathanBleeker wrote:If you right click on the menu manager shortcut and check what path it points to, where does it go?
"D:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Milviz\MV_MM.exe"

JonathanBleeker
Posts: 3446
Joined: Sat Mar 13, 2010 7:38 pm
Re: For the Win8 users...

Post by JonathanBleeker » Sat Mar 21, 2015 5:52 pm

When you make the changes in the addon manager, then close it, then reopen the addon manager, do those settings persist or is it just in the sim that they aren't showing up? If not...I just thought perhaps you may need to run both the menu manager and the ACM (the ACM is in your Prepar3D folder\Milviz\MD530\MV_ACM.exe) as admin.

cyberdal
Posts: 4
Joined: Tue Nov 25, 2014 2:20 am
Re: For the Win8 users...

Post by cyberdal » Sun Mar 22, 2015 5:49 pm

JonathanBleeker wrote:When you make the changes in the addon manager, then close it, then reopen the addon manager, do those settings persist or is it just in the sim that they aren't showing up? If not...I just thought perhaps you may need to run both the menu manager and the ACM (the ACM is in your Prepar3D folder\Milviz\MD530\MV_ACM.exe) as admin.
Thank you JonathanBleeker for your replies. The issues is now resolved. I once again did what you suggested and it is now working. However, I also did that before and it didn't work before. Since I first posted this issue, I have installed additional scenery and aircraft, in addition to messing with FSUIPC and confirming all the "launch as admin" suggestions. TBH, I'm not sure now what fixed it but to let everyone else know the MD530 and addon pack both work fine in P3D v2.5 and Win 8.1. Thanks again.


Locked

Return to “MD530 Support Forum”