WilliamB
-
Posts
55 -
Joined
-
Last visited
Posts posted by WilliamB
-
-
It has been a while since I worked with FSXSE and installed the DHC2 and DHC3. Seeing your picture of products I realized that the MVAMS was separate program. I uninstalled the MVAMS and the PC6. I reinstalled the PC6 and the MVAMS. Launched the MVAMS and opened it. The DHC2 and DHC3 appeared in windows and the setups for each could be selected. There was no window for the PC6. Looked in the (C:) \users\butle\AppData\Local\MVAMS\Configurations folder and found DHC2.ini and DHC3.ini files but no PC6.ini file. There was a PH6 folder under ....\configurations folder with a simulator.ini present but no PC6.ini. The MVAMS manual indicates the simulator.ini file places configuration selections in the sim Addon menu. I am wondering if for some reason my installation is missing a PC6.ini file? The MVAMS manual says when the MVAMS is run any compatible aircraft installed should show up in MVAMS window. Or is it possible that is the only menu available for the PC6? If so there are no options for radios, load, and state.
Thanks for your help.
WilliamB
Thanks. I will try Milviz.
WilliamB
-
It has been a while since I worked with FSXSE and installed the DHC2 and DHC3. Seeing your picture of products I realized that the MVAMS was separate program. I uninstalled the MVAMS and the PC6. I reinstalled the PC6 and the MVAMS. Launched the MVAMS and opened it. The DHC2 and DHC3 appeared in windows and the setups for each could be selected. There was no window for the PC6. Looked in the (C:) \users\butle\AppData\Local\MVAMS\Configurations folder and found DHC2.ini and DHC3.ini files but no PC6.ini file. There was a PH6 folder under ....\configurations folder with a simulator.ini present but no PC6.ini. The MVAMS manual indicates the simulator.ini file places configuration selections in the sim Addon menu. I am wondering if for some reason my installation is missing a PC6.ini file? The MVAMS manual says when the MVAMS is run any compatible aircraft installed should show up in MVAMS window. Or is it possible that is the only menu available for the PC6? If so there are no options for radios, load, and state.
Thanks for your help.
WilliamB
-
Not sure where this should go (also been to Milvix forum) but thought I would try here also. Recently purchased the Milviz Pilatus PC-6 through Orbx Central. After install I noticed no MVAMS set up for aircraft was not provided. It was provided in the Milviz DHC2 and DHC3 also purchased through Orbx Central. The PC-6.dll file is missing for the Pilatus PC-6. Can anyone provided some help on this issue.
Thanks in advance.
WilliamB
-
Thank you.
WilliamB
-
I have done what you suggested, Nick. Ran FSX with your scenery.cfg file without a problem. Third Party and Orbx sceneries were in proper location relative to the "UT Exclusions for Default Scenerys" insertion point. The Insertion point designations and listings did not change in Orbx Central. Do you think there is any reason to delete and reload Orbx Central? Erasing the scenery.cfg file and running FSX resulted in a strange result i.e. the scenery.cfg file produced by FSX looked like an old version of a scenery.cfg file for my system. For example "Addon Scenery" was the first listing. You were correct the fatal error is still present.
I am considering running the repair feature from the FSX Disc and/or installing a hard drive image I made about two years ago. The Administrator of RTMM and the MIsty Flying Club (MFC) has also offered to take a look at my system. He is also an expert. Will see how it goes. In the mean time all the Flying with MFC is in Alaska, eastern Canada, and the western US where I get no Fatal Errors.
I want to thank both you and Doug for all your time and help.
It was much appreciated!
WilliamB
"Ut exclusions for default scenerys"with the exception of pilots meshs which were below
-
1
-
-
Doug,
I did as you suggested and the insertion point list stayed the same. I am not sure why the drop down list is not changing.
I was looking at the FSX Scenery Library. I thought that all the 3rd Party RTMM scenery should be above all Orbx scenery's. The only RTMM scenery that is above all Orbx scenery's In the FSX Library is Scenery Area 524, the Area that is the insertion point for Orbx Airports and Regions. All other RTMM Scenerys are listed below the Orbx OpenLC Scenery's. Other 3rd party scenery's are located below the Last RTMM Scenery and thus are also below the Orbx scenery listings.
The order of scenery's in my FSX library follows: One third party Scenery-Area.524, Orbx Libs, Orbx airports, Orbx Freeware airports, Orbx Regions, NZ, AU2, OrbxOpenLC's, OrbxOpenLC Base, 3rd Party Scenery's RTMM, Anchorage Airport and Terrain, Aerosoft Beaver Mission Pack and Pier39, Tongass Fjords, UT Alaska,Default Scenery's, Orbx Global Vector, Pilot Meshs, Default Scenery's, Orbx Vector_AEC, Default Terrain. Don't know if this is helpful but thought I would list.
Appreciate your efforts.
WilliamB
-
1
-
-
Doug,
Scenery's areas [524], [398], [397], [396], [395], [394], [393], and [392] are scenery's listed from top to bottom of "Orbx Airports and Regions" listed in the insertion point list. Scenery Area 524 is at the bottom of the scenery.cfg file with the other scenery's occurring in numerical order in the scenery.cfg file. Scenery area 524 Is listed in the insertion below scenery area Of Orbx Airports and Regions. I searched the scenery.cfg file to locate the scenery areas shown in the insertion point list.
If anything is unclear let me know. I am perplexed and look forward to a solution.
Thanks,
WilliamB
-
Doug,
I want to be sure I understand your images and recommendations:
I am using the Scenery Library in FSX to show the order of scenery. Currently the order is not correct as most of the 3rd Party RTMM scenery is below Orbx OPENLC entry's. I believe this is because the insertion point listed is "RTMM-01-RTMM Object Libraries 1-2-3-4" the first scenery in the RTMM Scenery list. I believe this may be corrected when the insertion point for "Orbx Airports and Regions" is changed to "UT Exclusions for Default Scenery" (No. 378 in the Scenery Library in FSX) as you have recommended. When I click on the drop down arrow under "inserted below" I can only see 8 entry's. There is no way I can select an entry that is at no. 378 in the scenery listing. I did activate all UT scenery's listed in my FSX Scenery Library. What am I doing wrong?
The first image (used to show the placing of Tongass Fjord Scenery's) also shows the higher archy (correct location of all scenery types? The last image shows the Insertion Point screen in Orbx Central. It indicates the insertion point for Orbx Airports and Regions should be "UT Exclusions for Default Scenery". It further indicates the insertion point for "Orbx Global OpenLC" should remain as currently listed-"Orbx Airports and Regions".
Sorry I am not as conversant as I should be but the last time I worked with Orbx Central and the logic of insertion points was several years ago with the Older verision of Orbx Central. To your credit Orbx has automated most of what used to be done by the user.
Thanks for your help!
WilliamB
-
Nick,
I am interested in the change in the registry entry needed to assure acceleration can be activated. Do you have a reference to the registry change required? Do you think running the repair feature on the FSX disc offers the best chance of fixing the fatal error problem?
I also did not mean to conflate or confuse the fatal error with scenery order but I did think scenery order or missing scenery that was called for by the processor could be part or the problem. I went to the Orbx Central forum as I thought it was the appropriate place. I did not realize you could address scenery order and Orbx Central issues.
I will continue to work with Doug on it as I realize I am not very conversant with scenery order, insertion points, and how Orbx Central really works.
Thanks for time and effort to help on this issue.
WilliamB
-
Thank you your reply Doug,
I attached the scenery.cfg (9/3/2021) was created while I was trying to adjust insertion points. I accidently hit Orbx Airports and Regions which was placed in the "inserted below" below field. I believe Tongass Fjords was placed as the insertion point before my mistake. The OldScenery.cfg (8/31/2021) should show insertion points as they were before my mistake. I also included a scenery.cfg.backup-Orbx (1/9/2020) that was working well just after I setup of FSX.
I appreciate your help!
WilliamB
-
Thanks Nick for that information. I did not think FSX 2006 was compatible with windows 10. Am I wrong in that assumption?
A fellow on AVSIM responded to my placing the fatal error problem on AVSIM "Crash to Desktop (CTD) Forum". I mentioned using the repair feature on the FSX install Disc and he responded among other things that he could not get his FSX Disc approved for install and went to FSXSE instead. I am glad that microsoft still offers install appproval feature as I intend to continue to use FSX and may want a new install in future.
Do you think scenery order could result in the fatal error problem I am experiencing?
Thanks again your help is truly appreciated!
WilliamB
-
Nick,
I have a question that you may be able to answer. I have my original FSX Discs. I think microsoft has discontinued the software approval program but I ran the 1st install disc and it looks like I can run the repair option. Do you think this could fix the *.dll problem and there is also possibly a problem with the bin files in the weather folder in the fsx directory. I noticed a wxmapping.bin file that could relate to the fact that the fatal error does not occur when flying in western NAmerica but occurs when flying in eastern NAmerica. If I run it the repair function could it negatively affect my FSX installation? My understanding is that the repair function only repairs affected files and leaves everything else alone?
Thanks for your help.
WilliamB
-
I am trouble shooting a fatal error (listed under FSX support) that requires me to check/change scenery order. My version of Orbx Central is 4.1.39. I have a significant number of addon scenery's mostly RTMM, as I am a Member of the Misty Flying Club.
When I access the insertion points under settings the drop down menus under "Orbx Airports and Regions" and "Orbx Global open LC" only show 10 scenery items with no scrolling feature. I need to access Tongass Fjords to place it in correct location. Should the drop down menu scroll and show all the scernery's I have? If not is there something I am missing?
It has been a while since I have worked with scenery's and Orbx has done much to automate the process. I have never worked with the scenery configuration file. I recall an explanation of how to handle scenery and insertion points. If someone could point to that explanation I believe it would help me.
Any help would be appreciated.
WilliamB
System:
Win 7 Pro, i7-4790K, AMD RX580 8GB, 32GB Ram, FSX-10.061637.0, Orbx Central v4.1.39, Global Base Pack, Vector, Trees, Open LC North America, All North America Regions, Tongass Fjords,many Orbx Airports, Airport Pack, Many RTMM scenerys.
-
Thanks for the weather.dll file. I copied the file and pasted it to the FSX directory and selected replace the existing file. Ran FSX and the fatal error was still present. Would that the problem were that simple. I don't suppose i could have copied it into the directory incorrectly? It is strange that the error only occurs in eastern 1/2 of Open LC North America?
Your help is appreciated
WiliamB
-
I have been flying with the Misty Flying Club a virtual airlines that is part of Return to Misty Moorings website. I have been actively flying since before Covid. Flying started in Alaska and proceeded south down west coast of Canada and the United States. All Orbx regions were flown through. No problems occurred on any of these flights until reaching the Southern border of the US. On reaching San Diego our routes turned to the East. The fatal error occurred on a flight leg that flew north on the eastern edge of New Mexico starting in Dell City Muni (2ES) with stops at KCNM and KATS ending at Roswell Intl (KROW). The error first occurred enroute from 2ES and required a restart of the simulator. I began trouble shooting and found that any flight initiated at KCNM, KATS, or KROW caused the fatal error to occur while on the ramp. Further trouble shooting indicated; that if you draw a line on the Map north and south from Regina, Saskatchewan to Rapid City, South Dakota to Denver, Colorado-to Roswell, New Mexico all flights flown from airfields west of that line do not cause the fatal error and all flights initiated from airfields east of that line cause the error.
Information given on error:
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.61637.0
Application Timestamp: 46fadb14
Fault Module Name: weather.dll
Fault Module Version: 10.0.61637.0
Fault Module Timestamp: 46fadb59
Exception Code: c0000005
Exception Offset: 0001542f
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033Information on error code: c0000005 indicates it can be caused when an APP calls a memory location that is not present or not larger enough.
I have restored the computer to an earlier time to no effect.
Any thoughts your may have as to cause of solution to this would be appreiciated.
WilliamB
System:
Win 7 Pro, i7-4790K, AMD RX580 8GB, 32GB Ram, FSX-10.061637.0, Orbx Central v4.1.39, Global Base Pack, Vector, Trees, Open LC North America, All North America Regions, Tongass Fjords,many Orbx Airports, Airport Pack.
No MVAMS.dll file in Milviz PC-6 purchased from Orbx
in FSX Steam Edition Support Forum
Posted
Thanks I will try Milviz.
WilliamB