Badger26

Seems to be working now. I just scaled back my app sizes from 125% back to 100% and reduced AI traffic to almost 0%. I think it was mostly my AI traffic settings that was causing the crashing. TacPack seems to be up & running like normal now.

Think it may be an issue with a Windows update I'm pretty sure because I decided to uninstall to recent Windows feature updates and seemed to have worked then but when ever Windows decides to install the updates again it becomes wonky & unstable causing the crash & app compatibility issues within the app itself. Really wish  VRS would release a patch for this bug as there seem to be no legit permanent fix that I can make work.

On 2/14/2023 at 10:10 AM, longbreak754 said:

Without any details of the crash it is hard to provide help....

 

Look at the Windows event viewer to any errors occurring at the time you try to run FSX. and post the entire entry into the thread - for info an entry will look like this example but obviously with different details....

 

Faulting application name: couatl.exe, version: 2.0.0.2356, time stamp: 0x52702856

Faulting module name: couatl.exe, version: 2.0.0.2356, time stamp: 0x52702856

Exception code: 0xc0000005

Fault offset: 0x00002956

Faulting process id: 0x1fd8

Faulting application start time: 0x01cf97d662b274dd

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe

Report Id: 2cd0a798-03ca-11e4-aaf3-d43d7ee230d0

 

Another quick check to carryout is for non TacPack related issues that may cause such errors - namely a corrupt flight or logbook entry....do the following checks ONE at a time and in the order given - i.e. do the corrupt flight check and then test FSX....

 

Corrupt flight - locate the FSX.cfg file located at C:\Users\<AccountName>\AppData\Roaming\Microsoft\FSX  (NOTE the AccountName element is the name of the account you log onto your computer with)...Open the file using Notepad and find the SITUATION= entry located in the [UserInterface} section - it will look similar to this example SITUATION=C:\Users\Brian\Documents\Flight Simulator X Files\<Name> - the <name> could be anything or blank depending on what has happened and if you have saved any flight...

 

Simply delete every thing after the = sign so that the entry now reads SITUATIOM=

Close the file ensuring that you save the changes and start FSX....FSX will load the default flight (the ultralight over Friday Harbour) - let it run  for a minute or so and then exit the flight and close FSX so that new flight related files can be written....restart FSX to see if the problem is resolved.....note that any setting you have changed (such as time weather etc will be reset to the default so will need changing once the problem has been sorted.....

 

Corrupt logbook - NOTE ONLY do this if the corrupt flight procedure doesn't fix the problem - this will lose you any hours you have logged but we maybe able to resolve that once you have tested and resolved the problem....

 

The logbook entries are stored in a file called logbook.bin located at . "C:\Users\<AccountName>\Documents\Flight Simulator X Files"...

Rename the file to logbook.BAK and start FSX - a new .bin file be created...fly a flight for a few mins and then exit the flight and close FSX so the new file is saved - restart FSX to test if the issue has been resolved........

Issue still not resolved after all suggested fixes. I also notice an error line in red above the screen after it it loads & just before it cashed. Says something like; failed more than 100 attempts to reach sim connect. It pops up just after the Honeycomb profile loads. Some other options I'm thinking about trying is loading from a restore point or uploading one of my backup images to my hard drive then doing a complete reboot. That kinda fixed a similar issue I once had in the past.

1 hour ago, longbreak754 said:

I have this every now and then - it seems to happens most often after a Windows update...

 

A couple of things that usually resolves the issue...the TacPack one is usually the only one required... 

 

TacPack - With FSX closed start the TacPack manager (TPM) - if you have not created a desktop icon for it or are not sure where to find the app here's some info.....

 

An entry for the TPM can be found on the Windows Start menu under the Vertical Reality Simulations entry.... TIP to make is easy to access do one of the following - Right click on the TPM link and select the Pin To Start option (this will place a large icon onto right hand icon lists) OR select More>Pint to Taskbar (puts a small icon on your taskbar) OR my preferred option select More>Open File Location - this takes to .exe location...you can then right click on the .exe file, select Send To>Desktop (create shortcut) to place a icon onto your desktop....

 

I would also advise running TPM with admin rights  - this can be set to happen either by Right clicking the icon and selecting the Run as Admin option or if you right click and select properties - this will open a Properties window....on this window select the Advanced button and place a tick in the Run as admin option followed by Ok and then Apply...this will run the app in admin mode every time you click on it...

 

Once the TPM has started you may get a message about FSX running in a unsupported mode - can't remember the exact message as it quite long - and there will be a option to change the mode - do so, close TPM and then try FSX...

 

If the TPM starts with no issues or is the FSX error remains after changing the mode  you will need to provide more specific info regarding the issue....however, if you are certain that is is DirectX related I suggest downloading the DirectX Redistributable pack - this include DirectX 9 (versions A, B and C - C is used by FSX), 10 and 11 - it can be found HERE or HERE

 

Click on the download link provided 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. Allow the Installer to do its thing and once complete reboot using the RESTART option - The reboot is essential to allow the windows registry and important system files to be updated....Note that the install process will only install missing versions and/or replace missing/corrupted/incompatible files of the versions it finds installed....

 

Tried  the DirectX fix you recommended but I still have it crash on me. Even tried running TacPack in admin mode & still crashes. Tried finding a crash log but all I found was a page that just has a bunch of random code with no helpful info about why the game crashed.

Ran into yet another issue with TacPack today. It gives me an error message on startup then the sim crashes after it loads a flight & I try to do anything. it seems to be dll related and possibly a directx issue. anyone know of a fix for this?

On 1/28/2023 at 7:44 AM, longbreak754 said:

I don't think the default carrier has such a feature (BTW there are more than one carriers - google the phrase -FSX carrier locations' this will give you info on their locations...

I also don't think the carriers that are provide via the TacPack have the function either....

There are a number of freeware carrier addons that add additional carriers (and that TacPack can use) - one of the better ones is AICarriers, a google search should find it but it available here in the library at flightsim (note you may find multiple versions of this  app the best to get is the .net version (IIRC the file name for it here at flightsim is AICarrier.net)...

There are also some payware stuff out there but whether they offer such functions as moving lifts I don't know.... 

Yeah there doesn't seem to be at least in the Acceleration carrier. Be cool if we could control the lower deck lifts & have the planes moved & stored below deck while the ship is moving & also have it automatically load fighter aircraft with weapons & fuel. This seems like an awesome idea for an updated TacPack if VRS ever decides to make a new one for MSFS. I'm going to give AICarriers a try though.

I decided to re-buy TacPack & have been messing around with carrier functions today. Is there a way to lower the aircraft lifts to lower an aircraft to the lower hangar deck of a carrier? Trying it with the Acceleration carrier since that seems to be the only one in the system and with the F-35C.

I think it somehow got deleted. I'm thinking I may have to just bite the bullet and buy TacPack again with one of my alternate emails. Now that I think of it I may have used up my last remaining activation allowance on my last PC which I no longer have access to anyway. It's not that expensive anyway so I don't mind that much. Kinda wish the FSX version was free though or at least significantly lowered the price.

I just want to disable the alert so I don't have to see it every time the game launches. I don't care about the certificate and just want to play the game without always getting notified about it and it says the certificate is OK anyway so I just want it to quit bugging me every time I load up FSX. So does anyone know of a workaround to at least remove the pesky security certificate notification?

Alright so I fixed the weapons issue but now I'm having an issue recovering my VRS login to reactivate TacPack. Will be needing it since I'm installing a bigger internal C drive on my PC and may have messed up my product key when I moved my stuff to an external hard drive. I also tried a password reset and never sent me the prompt so now I'm in contact with customer support hoping to get a solution before I end up having to buy TacPack again VRS customer portal acts like my email is still active on their site but when I try for a password reset I get nothing sent and the customer support guy said they don't seem to have my email on file. Has anyone else had this issue?

Noticed a problem while I was messing around with the F-35 with TacPack addon over the weekend. The weapons don't seem to fire at all even though the addon is connected to the sim just fine. I can use VRS AI such as drones, carriers etc.& other features of the program and it reads my aircraft as a VRS surrogate but when ever I try switching & firing weapons of any kind nothing happens. The weapons do seem to be created because I can use the manual emergency release but the weapons buttons(pickle & trigger) don't work. Anyone know what could be causing this or have a fix for it? I payed $30 for this addon and just want it to work as advertised.

Seem to have fixed the axis problem(just had to set null to 0 and sensitivity to max for all the axis's) but now there are just two other issues I can't seem to fix. One; the lights won't turn on and two; the switch panel doesn't seem to work. Anyone know how to fix these issues?

Was very exited to get my brand new Honeycomb Throttle in the mail today but was really bummed to see that the throttle axis's are all screwed up and can't seem to pair them to the game properly. I can't seem to get it perfectly. Also it now makes the game throttle go the opposite direction n the physical throttle. Anyone know how to fix this?

Ok so it looks like it was a double install of FSX SE causing the issue. I apparently had a copy of FSX SE both on my internal C drive and a copy on my external hard drive. I ended up deleting the copy of FSX SE that was on my C drive and moved everything important to the copy on my external hard drive and it seems to be working now. Thanks everyone for all your help.

Anyone know where I can get the complete file folder of FSUIPC4? When I run the installer that came in the download it doesn't seem to go to where its supposed to go. I get the feeling the installer may have some bugs or something and wanna try putting the files in myself manually to see if that works.

I have both extracted the zip folder and ran the installer as other forums recommend but no luck. Here is the log as follows from my recent install attempt:

 

Installer for FSUIPC4.DLL version 4.974

 

 

Looking in registry for FSX install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"SetupPath"

... >>> OK! FOUND FSX!

SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX

 

Looking in registry for FSX-SE install path:

HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX

Parameter"Install_Path"

... >>> OK! FOUND FSX-SE!

SetupPath=F:\Steam\steamapps\common\FSX

 

Looking in registry for Prepar3D v1 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D

Parameter"AppPath"

... NOT found! ...

 

Looking in registry for Prepar3D v2 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2

Parameter"AppPath"

... NOT found! ...

 

Looking in registry for Prepar3D v3 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3

Parameter"AppPath"

... NOT found! ...

===========================================================

 

INSTALLATION FOR FSX:

SetupPath="C:\Program Files (x86)\Steam\steamapps\common\FSX"

Checking version of the FSX EXE:

... Version 10.0.62615.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 62615 (Steam)

Found SimConnect build 61259 (Acc/SP2 Oct07)

NOTE: This is actually FSX-SE masquerading as FSX-MS

Checking if there's already a version of FSUIPC4 installed in:

C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL

... Version 4.974 found.

Installed version is later: it is not overwritten.

Looking for the current user's Application Data path:

... found as "C:\Users\agrim\AppData\Roaming"

Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one

Looking in "C:\Users\agrim\AppData\Roaming"

... No FSX_SE.CFG there

Looking in "C:\Users\All Users\AppData\Roaming"

... No FSX_SE.CFG there

Looking in "C:\Users\Default\AppData\Roaming"

... No FSX_SE.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

... No FSX_SE.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

... No FSX_SE.CFG there

Looking for the current user's Application Data path:

... found as "C:\Users\agrim\AppData\Roaming"

Now finding \Microsoft\FSX-SE\FSX.CFG for all users, including this one

Looking in "C:\Users\agrim\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\All Users\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

... No FSX.CFG there

Looking for the current user's Application Data path:

... found as "C:\Users\agrim\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\agrim\AppData\Roaming"

Found FSX.CFG in "C:\Users\agrim\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

(for FSUIPC4, without Loader)

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... No SimConnect.XML file found. This is okay.

Looking in "C:\Users\All Users\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

... No FSX.CFG there

"Modules\FSUIPC Documents" folder already exists.

Now installing additional files into the "Modules\FSUIPC Documents" folder:

Installed "FSUIPC4 User Guide.pdf" okay

Installed "FSUIPC4 for Advanced Users.pdf" okay

Installed "FSUIPC4 History.pdf" okay

Installed "The 2016 List of FSX and P3D Controls.pdf" okay

Installed "FSUIPC Lua Library.pdf" okay

Installed "FSUIPC Lua Plug-Ins.pdf" okay

Installed "Lua License.pdf" okay

Installed "Lua Plugins for VRInsight Devices.pdf" okay

Installed "LuaFileSystem.pdf" okay

Installed "Example LUA plugins.zip" okay

Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay

Installed "Offset Mapping for PMDG 737NGX.pdf" okay

Installed "Offset Mapping for PMDG 777X.pdf" okay

Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay

Installed "FSUIPC4 Offsets Status.pdf" okay

Installed "Profiles in Separate Files.pdf" okay

Installed "FSUIPC4_Loader.dll" okay

===========================================================

 

All installer tasks completed.

Registration dialog 'not now' selected

*************** End of Install Log ***************

I've been trying to get FSUIPC4 to work on FSX SE but for what ever reason I can't seem to get it to work. I know FSX is a bit dated these days because of the new MFS but I still like to use FSX sometimes for certain addons that I like. I've been trying to get FSUIPC4 to work to get a glass cockpit app that requires me to use Peixsoft Connector to link the sim with my tablet. So far I've tried both extracting the file to FSX/Modules folder, rearranging the program pages within the module folder and also did an uninstall & reinstall of FSX but no matter what I do FSUIPC does not appear in the addons menu and Peix Connector won't work with my tablet no matter what I do. This is a free unregistered version FSUIPC but its worked just fine before for what I'm trying to use it for without having to buy a registered version. Can anyone help me here? what I'm trying to use it for. Can anyone help me out here?

I fixed the issue. Turns out the gauges was in the form of a cabinet(which threw me off because I'm so used to them being in their own file in the addon itself and automatically included at install or using native FSX gauges) and had to put them in the FSX/gauges folder manually. I guess the problem was caused by when I did a clean uninstall & reinstall of FSX to fix an unrelated issue and the Sus Scrofa gauges got deleted in the uninstall.

For some reason all the gauges for the Sus Scrofa addon are no longer in the main file and when I launch the addon the gauges are just black circles and squares. Anyone know how to fix this? The main screens seem to work fine but those provide very basic and little info. Screens that show the altimeter, fuel levels, compass and stuff like that are blacked out. I tried a fresh re-download of the addon and got the same issue.

So I finally got it to work. Instead of doing an uninstall and reinstall via Steam I ended up deleting all local FSX related files on my PC and then did an uninstall and reinstall via Steam free of addons and other software. Not sure what it was but maybe one of my addons was probably interfering with functions and features of other addons. Reinstalled the Honda Jet and nothing else and now window curtains in the cabin and all cargo doors work as they should.

I don't get why addon developers have setup extra cargo doors and window commands this way but they all seem to be programed to a combination of [shift+E] followed by a number which isn't working for any of the addons that have operable cargo doors or window shades in all my addons that have them even the payware C17. The most problematic seems to be on the Honda Jet freeware addon for FSX. For some reason the window curtains or cargo doors no longer open or close as they should. I've managed to get the front cargo doors to open a few times but the majority of the time it doesn't work at all. I even tried doing a full uninstall and reinstall of FSX with no other addons but the problem still persists. I also tried altering the aircraft config to use a different key command and still doesn't work. Does anyone have a fix for this?

Just had the issue crop up today when trying a flight from LAX to Vegas. Any news on a recent fix? FSUIPC no longer seems to want to fix it anymore. Before the FSUIPC I got(the free unregistered version) fixed it like a charm. Now nothing.

Agree. You can't expect perfection with freeware addons. Some freeware addons are so good they come close to payware such as some of the mega pack aircraft addons but they all have their own little problems and issues that I have learned to expect. I wish some developers would occasionally test and fix issues though. I'm still having issues with custom commands for opening cargo doors and window shades in some freeware addons such as the Honda jet. I've been having issues with the config file that comes with the download of that particular addon.

Yeah it is a weird design. I just have engine auto shutdown set to off and engine autostart set to R. L & Both aren't even programable in FSX for some reason. Engine autostart/shutdown works for all engines automatically. I think they based it on twin engine starters like the ones in Beechcraft airplanes.

So far I've been using Honeycombs Alpha yoke and have been very pleased with it. Plan to get the throttle and eventually pedals & when they come out(if ever) I think once Honeycomb has all three controllers they should consider selling them all as a set for a few hundred dollars(maybe 600 to 700 USD for the yoke throttle and pedals seems fair) I'd happily sell my yoke for a complete Honeycomb kit so I can have a nice Honeycomb flight control ecosystem that all goes together nicely. For now I'm just using a Thrustmaster throttle and Thrustmaster pedals which are just Okay. Also speaking of when were the Honeycomb Charlie pedals supposed to come out? There were slated for last year(2021) but nothing since the delay announcement. Have not seen them posted for sale anywhere.