longbreak754

Hi Rick,

First, welcome to the forum...

Second, I assume that the JF Vulcan is on DVD because that is the only media medium that I know of on which it was distributed - the product is 'old' and pre-dates digital style downloads.

The link you provide only shows the FSX/P3D versions of the Vulcan and a search for JF products and FS2004 products in general show no FS2004 Vulcan products.

If, as I have stated, the product is on DVD the probable cause of the issue is due to a security related feature called SafeDisc and the removal of an associated system file SECDRV.sys required to allow SaFeDisc to be recognised.

Due to well known security related issues with SafeDisc, Microsoft took the decision to ship Win 10 without the SECDRV.sys file. They subsequently then issues patches to disable it in earlier Win versions - see HERE for some general info or use the search phrase safedisc windows 10 in google to view other sites with relevant information on the subject.

Unfortunately, in Win 10 there is no easy way to resolve the issue. One option is to copy the contents of the disk to your hard drive. You can then attempt to install it from there - do so using Admin rights by RIGHT clicking on installer file and selecting Run as Administrator from the resulting options...

Recently I purchased a dell gaming computer...

 

AND

 

...I already ran all the required computer updates...

So a new vanilla Win 10 install and, one assumes from the update statement, the latest available Win 10 updates.....

The issue, as stated, can sometimes be caused by a DirectX (DX) issue, especially if DX10 preview is selected. So go into settings and disable the DX10 Preview option if set and test.

WRT FSX-SE versus the boxed Gold version - As I have yet to install the -SE version (brought a copy when on sale as a 'digital' backup to my original DVDs) I don't know if any of the following libraries are automatically installed as part of -SE install process. For completeness it is worth noting that -SE was rebuilt (updated) using the Visual C++ 2013 compiler for better optimization and performance. However it still makes use of the 2005 library for backwards compatibility,

That said, it is also possible that the OS is missing some key FSX related 'older' essential libraries...by default, Win 10 ships without some of the earlier versions of such libraries that FSX (and other 'older' programmes) require. The key libraries are listed below...

You can use Programs and Features to check if you have any of the following 'libraries' installed or, if you wish, simply download and install them - the installers will check for any previous install and will replace any missing/invalid/corrupt files or install the complete package as appropriate.

With the exception of DX, you will need to download the relevant 'bit' version for your OS (i.e. 32 or 64 bit). DO NOT run the installer directly from the download option but select the Save As option and save the file to temp location. To install, right click on the file and select the Run as Administrator option. Install each package separately, starting with the oldest version, and reboot using the RESTART option between each install. The reboot is essential to allow the windows registry and important system files to be updated.

Direct X (DX) - FSX requires version 9 (actually 9c to be specific), and although it is included on the installation disks, it is woefully out of date and incompatible with Win 10 (Win 10, depending on the build state source file, only ships with v10 or above). I suggest that you download and install the DX Redistributable pack from HERE. The pack includes versions 9, 10 and 11 and the install process will only install missing versions and/or replace missing/corrupted/incompatible files of the versions it finds installed.

Visual C++ Runtime Redistributable packs - specifically version 2005 and 2008 but I also recommend installing 2010 as well. You can find download links for earlier versions HERE.

.NET Framework - specifically versions 3.5 and 4 - download from https://dotnet.microsoft.com/download/dotnet-framework

It is worth pointing out that you can have multiple versions of these 'libraries' installed. As previously stated, they are not just required by FSX but are used by many other programs and apps. They will work happily along side each other and a program or app will automatically use the most compatible version.

@ Rescue 936...

You may be interested in looking at this WEBSITE...

Its contains lots of military based AI packages, scenery, etc, including a number of UK bases (current and closed) such as Coningsby, Marham, Valley, Leeming, Lossie, Kinloss, Linton plus USAF bases such as Lakenheath and Mildenhall, just to name a few.

Some of the scenery is basic updates to FS2004 defaults whilst others are a complete rebuild with custom scenery.

You can freely browse the website to see whats on offer but you must have a free registered account to download

Give us some more details....

Are we talking about the default FSX airport?

If not what is the name of the scenery package and where did you get it?

...

 

I would rather just BUY AI programs then mess around with all the details. So it might be worth it to just get the latest Traffic Global from JustFlight and EVERYTHING would be refreshed.

Just so that you are aware the Traffic Global (TG) product currently does not contain Military based models and flight plans.....whether they intend to do so a later stage is unknown - haven't been to the dedicated TG forum page for a while so that may be place to check if they intend to.

A very good alternative for Mil based AI is Military Ai Works (MAIW - see HERE) - originally MAIW offered only FS2004 based stuff (most of which worked well in FSX once the flightplans had been converted) but they now produce many FSX/P3D conversion packs for older stuff and now offer most new items in FS2004/FSX/P3D.

You have to register to be able to download (its free) but you can browse the site without registering to see whats on offer.....

The files are stored on your rig within the main steam folder...

The default install path for Steam games such as FSX is C:\Program Files\Steam\steamapps\Common - within the common folder there will then be a folder for each Steam game you have....

After that the folder structure follows the games OWN folder structure so for FSX you will see such entries as Scenery, Texture, SimObjects, Effects, Gauges, Sound and Addon Scenery to name a few....

If you can wait until Black Friday (Nov. 27th), it's very possible that FSX-SE will be insanely cheap.

It isn't just on sale during the advertised Black Friday event. Like many items on Steam, it goes on sale quite regularly for short periods - usually anything from a short 24 hour period up to a week or so. However, these sales are not generally advertised but are buried deep in the offers section....

To be notified when an item is on sale simply add it to your wish list - when the item is on sale you will be notified by email...

A possible reason could be the size of the parking slot versus the size of the aircraft...

IME the AI engine will happily send a small aircraft to a large spot but will not send a large aircraft to a smaller spot where the aircraft won't fit...

+1 on Charlie's comment...

I have also regularly used an assigned parking code entry in user aircraft to be able to park at specific areas of an airport - hence the reason why I provided the info....

In the example given, the code used is the one used by a MAIW provided MV-22 Osprey AI package. Each and every time I have landed at MCAS Miramar, I have been directed to a spot dedicated to the VMM-161 AI, as provided in the airport .bgl file. I used to also have the V22 entry along side the V161 code but would often get sent to a one of the generic V22 only coded overspill spots or, occasionally, another VMM parking area that was coded with both a Vxxx code and V22.

I considered mentioning the possible need to amend an airport using ADE but, as stated based on the limited info given and as we are talking about a VA, I posted my reply on the assumption that any airports used by the VA will have suitable and readily available scenery, either via the VA site or via a recommendation list.

There are TWO elements that control assigned parking - one is aircraft based and the other is airport based...

I assume you need to assign the codes to a user aircraft...

You will need to edit the appropriate texture entry in the aircraft.cfg file. Use notepad to open the file and then add the entry as highlighted in BOLD in this example...

[fltsim.4]

title=Virtavia MV-22 Osprey VMM-161

sim=Osprey

model=

panel=

sound=

texture=vmm161

kb_checklists=Osprey_check

//atc_id_enable=00

atc_id=168033

atc_airline=HAWK

atc_flight_number=33

atc_parking_types=MIL_COMBAT, MIL_CARGO

atc_parking_codes=V161

ui_manufacturer=Bell-Boeing MV-22B Osprey

ui_type= -

ui_variation=168033/YR-00, VMM-161 'Grey Hawks', MAG-16, MCAS Miramar, CA

ui_typerole="VTOL transport"

ui_createdby="Virtavia"

atc_id_color=0x00000000

atc_heavy=0

atc_id_font=Verdana,-11,1,600,0

prop_animation_ratio = 1, -1

description=168033/YR00, VMM-161 'Grey Hawks', MAG-16, MCAS Miramar, CA

If you need to add 2 or more codes they need to be separated by a comma e.g =V166, V22, SFA

It was the game bar that was on. I don't know how it got turned on.. So I turned it off and things work well again.

 

Thanks Robin. Win 10 seems to be so complicated !!!!!!!!!

For future reference, so you are aware, Win 10 updates can be effectively categorised into three types - Major Version updates, Security updates and Feature updates....

Major version updates happen twice a year (usually late March early April) and can be considered as a new version. Many people seem to have big issues with these updates as they can 'reset' file associations and app setting to default - i.e. turning the game bar on....

Security updates are normally rolled out monthly but can occur more frequently...

Feature updates are again, normally rolled out monthly but, like Major updates, they can cause 'reset' issues...

Personally, I have not had any issues with win 10 updates (have 2 relatively old rigs running it) but my next door neighbour seems to have no end of issues each time he updates his main family pc which is only 11 months old - his older laptop (about 3 years old) had a few 'reset' issues at the last major update to release 2004 back in May which I help to resolve

As Wim has pointed out Stock NavAids cannot be edited....

However, a possible (unrealistic) solution to what you want to achieve may be to add an new additional user created item - see section 8.4 (page 123) of the user manual....

Depends on what the object is....

If standard object like Aprons, runways taxiways you can use the Unlock menu to unlock all similar items - i.e if you select Aprons it will unlock ALL locked aprons...

If an non standard object (i.e a library object) say a hanger or hangers you must select the item by left clicking on it and then right click and click on the Lock Object option - if an item is locked there is tick next to the Lock Object listing...

Its so sad when such things happen....

Hopefully the offending SOH member in question is given a lifetime ban from the SOH forums....

 

.....could not find one for 05, which was also recommended...is this needed ?)

 

Hi Neil

 

Yes it is needed. You can find download links for earlier versions HERE

 

You will need to download the relevant 'bit' version for your OS (i.e. 32 or 64 bit). Click on the required link and a standard download option box will appear - DO NOT run the installer from this but select the Save As option and save the file to temp location. To install, right click on the file and select the Run as Administrator option. Install each package separately, starting with the oldest version, and reboot using the RESTART option between each install. The reboot is essential to allow the windows registry and important system files to be updated.

As it is Win 10 and there has been a MOJOR update it is likely that the problem is related to a Windows setting regarding power saving on USB ports...a similar problem was found to be the cause of another joystick problem I replied on a couple of weeks ago...

See this THREAD

Could a corrupted assigned control listing file...Try the following...

1. Go to C:\Users\AppData\Roaming\Microsoft\FSX\Controls

2. Check the contents of the folder - unless you have made any backups there should only be one item, a file named Standard.XML.

You now have two options...one simple and one that requires some work but will retain all of your own changes to default key setting and possibly your HOTAS settings....

Option 1 - Rename the file to Standard.xml.BAK or Standard.BAK. Start FSX and a new file will be created setting all control listings to the FSX default Close FSX to allow the new file to be saved correctly. Connect the HOTAS and start FSX and then try to configure it.

Option 2. Make a backup copy of the Standard.xml file for. Open the file in Notepad and look at the contents. The file lists the key assignments. They are listed under specific area titles that appear as the very first entry of a specific listing to distinguish them. Normal FSX default settings areas are KEYBOARD_MAIN, KEYBOARD_SLEW, MOUSE_YOKE and MOUSE_SLEW. Any added controller will then have its details added below the last entry of preceding section and will appear something like this example:

Logitech Extreme 3D{93943310-477F-11E5-8001-444553540000}

NOTE: there will probably be several entries for the controller....

Each section has a specific START and FINISH function instruction point entry that acts as a ON OFF switches - namely and that must be present for the area (and controller) to be recognised

Either scroll down the listing to find any controller entry or use the Find option by typing the phrase

into the search field - this will then take you the END of each section listed. The next immediate entry should then be a new START function entry e.g.

Check to make sure that all section entries are correctly configured and amended if necessary...

Try this....

Rename the current fsx.cfg to fsx.cfg.BAK and then run FSX - a new fsx.cfg will be built.

If FSX runs ok you can cross reference the new .cfg against the old one to re-instate any tweaks you may have made...

 

oh, and longbreak, your scenery.cfg was most likely re-numbered by SCE. That program has an option that does that.

----

I am aware of the option - as I mentioned in my last post I have created a number of selective area .cfg files. Before settling on my current method I experimented with a number of ways of doing so and used the numbers reset option on a couple. As I have never changed the priority listing for default areas in any of my .cfg files the Area and Layer numbers have remained consistent. In my experience of using the feature it only changed the Area.XX number to fill missing gaps so that the numbers were sequential - it did not change any numbers for those already in sequence. Again, the Layer numbers were only changed to reflect the new Area.XX number.

However, the file I used to create the example entry is a copy of the original file created at around the time I installed FSX - this is clearly indicated by the date of it (22 Feb 2014) and has never been edited or even opened in SCE.

I have two rigs with FSX installed and have always stored the vast majority of non payware scenery outside of FSX in a dedicated folder structure which I keep up to date on both machines (i.e. if I add new scenery to PC 1 and intend to keep it I then add to PC2, manually editing the appropriate selective scenery.cfg file) as well as a single manual backup on a removal drive .

After the initial install test and activation process I simply copied the complete scenery over along with the current in use and selective area .cfg files. The entire contents of other relevant folders that also contain scenery files related to addons, such as the main Scenery\World folder for example, are also copied to ensure both rigs have the same setup.

@ johnhinson

Hi John,

Your reply got me thinking. Checked what I will refer to as the FSX default backup file - the scenery.cfg file located in the root directory of FSX - and it lists Area.119 as Edwards.

Checked my 'live' file for changes and it appears at some stage my Area.120 (default Addon Scenery) has become Area 115 and all areas are out by one. However, as the Layer= numbers are all the same as the area number would indicate that I have not change the listing myself - if you change the priority listing the Layer= number changes - its the Layer= number that dictates in what order the scenery is loaded into memory. My assumption is that, although I can't remember for sure, when I first installed FSX years ago (this install dates back 2014 when I got the rig) I only installed the Deluxe part at the time and then installed the Accel pack later. However, everything works fine so no issue...

@ CRJ_simpilot

+1 on using SCE. I have used for a number of years mainly to create selective area .cfg files. Day to day, however, I tend to add new scenery entries manually.

@ il88pp

As indicated by Loyd a 'Remote Scenery Path' based error does not automatically mean that the folder is missing - IME it is always due to a cache error as described by Loyd.

@ Iilvaudais

Hi Loyd,

Thanks for the 'endorsement' - you beat me to it with the explanation....

Hi pomak249,

This appears to be a duplicate post by the OP - see HERE

I suspect that the OP has not got reply notification enabled so does realise his query has been answered - have PM'd him

In this instance removing the entry is not as simple as that because, unless the OP has made major changes to the priority listing, the area in question is a default FSX scenery area and its removal from the list MAY impact a large area of scenery within the sim...

A couple of simple solutions depending on your current install state with regards to installed scenery....for all options make sure you have the correct file as there are various copies of the the file within FSX/FSX-SE but only one is the 'live' data file read at startup to 'load' the scenery into memory. Make a backup of the original file before hand by making a copy of it. The live file can be found at C:\ProgramData\Microsoft\FSX or C:\ProgramData\Microsoft\FSX-SE - this will depend on the circumstances when you first installed SE - if you had the boxed edition of FSX still installed then SE will be installed at FSX-SE, if you didn't have a boxed version installed it will be at FSX.

Only have default scenery installed (i.e. no other addons):

Option 1 - Delete the scenery.cfg file - Start FSX and a new file will be created. This will give you a new scenery.cfg file with only the default scenery entries. If the same error exist after this try option 2.

Option 2 - Validate/verify the install. You do this in your steam account. Google is your friend here to find out how to do it. This will check all of the installed files and replace any missing files. Once the process has finished reboot the PC using the appropriate method for the OS in use -

Win 10: by using the RESTART option.

Win XP/VVista/7/8 etc: by shutting down and then restarting the PC.

If you have addon scenery installed:

Method 3: Edit the scenery.cfg file:

1. Open the scenery.cfg file in notepad.

2. Locate the area.120 entry - it will look similar to this entry but NOTE that the specific entry details may be different - the item I have highlighted in RED is the important one:

[Area.120]

Title=Edwards_AFB

Local=Scenery\Cities\Edwards_AFB

Layer=120

Active=TRUE

Required=FALSE

Note that, in this case, the RED entry starts with Local= and is followed by the listed scenery's location (in this case it is pointing to FSX\Scenery\Cities\Edwards AFB). In your case, based on the error message, the entry will probably state Remote=

If all the other details are there (i.e. there is a location as per the example) simply change Remote to read Local. Save the file and test....

Option 4 - If you do have addon scenery installed you can still use Method 1 listed above but, as indicated, the new ,cfg file will only contain the default FSX scenery entries. You will then have to either re-activate any addons OR use the info in the backup copy to cut and paste the entries of the addons into the new scenery.cfg file.

A slightly different view to expand on Charlie's suggestions:

AI Aircraft - Most users will simply put them into the appropriately named default folders contained in the default SimObjects folder but you can create new folders to hold them - for example AIModels or AIFastJetModels etc.

To do this you simply need to create the holding folder within the SimObjects folder (or outside if you wish) and then add a path entry in the [Main] section of the fsx.cfg file so that FSX can find them - here are examples of changes required:

[Main]

User Objects=Airplane, Helicopter

SimObjectPaths.0=SimObjects\Airplanes

SimObjectPaths.1=SimObjects\Rotorcraft

SimObjectPaths.2=SimObjects\GroundVehicles

SimObjectPaths.3=SimObjects\Boats

SimObjectPaths.4=SimObjects\Animals

SimObjectPaths.5=SimObjects\Misc

SimObjectPaths.6=SimObjects\AIFastJets

SimObjectPaths.7=SimObjects\AIHeavies

SimObjectPaths.8=MySimObjects\AIHelicopters

SimObjectPaths.9=C:\MySimObjects\AITrainers

The first 6 SimObjectPaths entries (0 to 5) are the FSX default items. Entries 6 and 7 are holding folders created within the default SimObjects folder. Entry 8 is a new holding folder created outside of the default SimObjects folder but still inside the main FSX folder. The last entry is an example of folder created outside of FSX - note that, in this instance, you have to provide a full path name including the drive letter.

Addon Aircraft - you could use the same principle as outlined above for AI but IME they are better off being placed in the default folders. Most payware addons will automatically suggest to install into the default location but you can usually select a different location. But note that not all payware will allow this and some will only install into the default location.

3rd Party Scenery - Again you can create a folder structure to meet your needs inside or outside of FSX - even on a different drive(s) if space is a problem. As with payware aircraft, most payware addon scenery will act the same as described above.

The important things to remember are these:

1. All scenery files (i.e those that have a .bgl extension) MUST be placed within a subfolder called Scenery.

2. All texture files (i.e .bmp, .agn, .dds) MUST be placed within a subfolder called Texture.

3. The scenery location must be known to FSX i.e activated - achieved by using the Scenery config page and pointing to the folder system when activating the scenery.

To clarify points 1 and 2 - Say you create a new folder called Scenery A and then:

1. Simply place all the files in the folder - the scenery will not display and may cause issues with other parts of the immediate area or in rare cases cause FSX to crash.

2. Create a Scenery subfolder (e.g Scenery A\Scenery\) and place all files into the subfolder - at best the scenery may partially display the scenery (namely those elements associated with the .bgl files (airfield runway, taxiways etc) but not display any texture based elements etc. At worst, it will display nothing or cause issues with other parts of the immediate area or again, in rare cases cause FSX to crash.

3ed Party Timetables - The accepted default location for traffic files is FSX\Scenery\World\Scenery folder but as they are essentially scenery files (they have a .bgl extension) they can be placed in any active scenery location - again inside or outside of FSX.

Another important thing to think about (touched on briefly by Charlie with his reference to any included README file) is that some scenery may include extra files that must be placed in specific folders for it to display correctly. A common example is if the altitude of the new scenery is different from the original FSX default. This is normally accomplished by the inclusion of a custom .bgl file that must be place in the default Scenery\World\Scenery folder. Some will also contain 'global' texture files that will need to be placed in the Scenery\World\Texture folder