MatzWarhog

Is this a Bug that has been reported, or is there something wrong with the altimeter only on the Syria map? When parked at, let's use Ruwayshid for example, the altimeter cannot be corrected to 0ft AGL while on the ground. The closest you can get by adjusting the Altimeter is 1000ft AGL. That is as far as the QFE will allow you to correct, and the radar (Elect) altimeter does nothing. Therefore, after take-off, your altitude is (X)+1000ft. This is the case at multiple airfields in Syria, and makes your altitude incorrect not only on take-offs, but on approaches as well. Anyone have a clue what the issue is that needs to be reported? Thanks!

Thanks for this tip Tripod! My throttle bricked in 2019 after I had not been flying for a few years due to work travel/life/etc/. I started a "support case" with TM over a year ago, and repeatedly told them I just wanted a new PCB. Emails went unanswered, then when they did, there was no response to "Please just sell me a PCB!" I finally was able to get one ordered recently that I am waiting on to arrive now. Last night I began reading threads on the TM throttle issues and stumbled upon this post, and figured, why not give it a try. After 10 minutes of trial and error today with a cheap USB hub and a long USB extension cable, and adding a few other peripherals on the USB hub... Bingo! My 3 year dead throttle lit up, and I spent this evening refreshing my set up and flying! I have the same issue with the rotating dial lever that I use for zoom as LanceLynxx above mentioned, but I was flying tonight! I should have a new PCB here soon, but I'll be putting it in a throttle and a reworked "cockpit"! Awesome temp fix! Thank You!!

I moved everything to a 250 just now. My concern is for the F/A 18 module bundle, it states it needs 120gigs free, and I only have 90 free.

I read you can install modules to your Saved Games folder on your C/ drive. Considering that my DCS is on a separate drive now, I would have plenty of space. Is that still possible to put them there rather than in the program file? Be just be time for a bigger drive just for DCS. It's a sweet simulator, but it's absolutely huge, ya gotta admit that. *Also, I haven't updated my signature, so those specs have been increased/changed

Sorry, just saw this. I went ahead and did it the hard way. Copied my Saved Games folder, did a total reinstall, then pasted my old Saved Games over the newly created folder, worked out great, except my DCS folder is 130GB and I can't find any files to delete under DCS/_downloads to free up enough space for new modules. Hmmm.

Correction! After checking, my sim files are in the Programs folder. So basically just copy and save the "Saved Games", reinstall everything on the larger SSD, and then replace the new "Saved Games" folder with the old one?

Somehow, I installed DCS world and my modules in my "Saved Games" Folder. It will have to be removed, so I'm curious what all folders I need to save before clearing it from my boot drive. I must have done this while in the Officers Club after a few too many...

Currently, all my DCS is installed on my boot drive SSD, but after adding the Nevada and Persian Gulf modules, I don't have enough free space to add the F/A-18C the Carrier and the Su-33 that come in the bundle. I have another SSD with plenty of room for all my modules. In my Users/Me/saved Games folder, I was planning to harvest the files I need to keep for control settings etc., uninstall everything DCS from the C Drive and install all of it together on the free'd up SSD. Anyone have suggestions I might be missing, or other recommendations that might help? I plan to tart flying the A10C online again, and am itching to fly the F-18C, and don't want any hiccups along the way, after the move. Suggestions welcomed! Thanks In Advance!! Matz

Excellent suggestion!!! I have several small/miniature SPST switches, that came with several colored rubber "caps" that are intended to make the switches easily identifiable. About to check, but I'm almost sure they will fit snugly, and nearly double the length of the slew stem. :thumbup: Matz

I'm not going to belabor the point that the phraseology "(effectively "refilling" your serial number)." in the document is worded incorrectly. However, if one takes your reply verbatim, no one's serial number will ever be "effectively refilled" (10 is refilled to it's original state, 1 is not). If I run out, I'll buy more as the cost of the software is insignificant when compared to the cost of hardware.

"1 activation is added automatically once per 31 days (effectively "refilling" your serial number)." is the kicker. If my doctor tells me to take 1 pill per day, that would mean 31 of them in May, not 1 and then stop. The way it is phrased in the included .pdf in the DCS files... in 10 months, you would be back to your original ten, as long as you didn't have to reactivate during those ten months... hence "(effectively "refilling" your serial number)." If that's not what it was meant to import, then that should be changed, as it is grossly misleading.

From DCS FC3 Quick Start EN.pdf: -StarForce ProActive AAA Technology You will no longer have a fixed number of activations, but in an effort to prevent piracy the system does limit the number of activations per month. Your game serial number will initially have 10 activations and when they all are spent, 1 activation is added automatically once per 31 days (effectively "refilling" your serial number).-

Then why does the documentation state use the phrase "(effectively "refilling" your serial number)."? A "refilled Serial Number would have 10, not 1.

After searching to find the above, it also states: "1 activation is added automatically once per 31 days (effectively "refilling" your serial number)." So by that statement once "PER" 31 days, would mean you would have your 10 activations back in less than a year. Correct?

On a side note, keep in mind that the heading for Runway 07 at Kobuleti is 64 degrees, not 70. Until I printed good charts, I had no idea how different the True North azimuths were versus the actual runways path. Matz (sorry if that is elementary info for some, but it wasn't for me when I really started digging into the details.)

Well I'm there on the A-10C now. Thanks to your help in the "Bugs" forum, and a fast CPU, it is all running very well!

Thanx for the quick response all the same SkateZilla... we were clearly posting at the same time.

Disregard... I just went to the registry and deleted the FC3 Key. It then allowed me to activate FC3 (using yet another activation). Hopefully, both Sims will remain stable now for a month so I can start gaining activations back. All of the reinstalls, and hardware changes were done in order to get the software to perform in a stable fashion. A bit disheartening when I invest time and money to upgrade my rig to run DCS the way it should run, only to lose the activations I bought in the first place. Surely there has to be an easier way to save your activations (short of a service ticket) just because you upgraded hardware. Problem solved, so no worries, as long as everything remains as stable and FAST as it is now. Matz

I just replaced my CPU (which by the way fixed ALL of my crash issues etc.) and I ran the A-10C specific registry .exe from the 'sticky' above, and it was successfully activated. However, FC3 will hang up and not activate. I see in the sticky thread that are are the specific files for the A-10C (which worked) but none for the FC3. I tried the "generic" link above the "Update" for specific modules, and was thinking to use that for FC3... but that link is dead, 404 error. What steps do I need to take to get the FC3 registry cleared so I can activate it? I can still fly the A-10C, but after every mission, it asks my to activate FC3... I stuck in a loop of it not allowing me to activate FC3. Thanx, Matz

I thought it was in the users downloads... not there now. Hummm... not sure.

beniboy's keybord maps along with the DCS Encyclopedia are must haves! Thanx to all that put together these awesome pieces of work!!

Thanks SkateZilla! That's the first time I've seen that recommendation! With the exception of 1-3 video 'hicups" (as in when pulling out of the hanger), I just flew "Hideout" for over an hour, and never had FPS <25... most stayed in the 50+fps range. :thumbup: Matz

So what does everyone see wrong in my crash files? I have read a large number of threads like mine that end with no solution.

Thought it was easier to scroll... dcs.zip

00101.514 INFO COCKPITBASE: HYDRAULIC_SYSTEM 00101.514 INFO COCKPITBASE: IFF 00101.514 INFO COCKPITBASE: HARS 00101.514 INFO COCKPITBASE: HSI 00101.514 INFO COCKPITBASE: NMSP 00101.514 INFO COCKPITBASE: ADI 00101.514 INFO COCKPITBASE: SAI 00101.514 INFO COCKPITBASE: LIGHT_SYSTEM 00101.515 INFO COCKPITBASE: FIRE_SYSTEM 00101.515 INFO COCKPITBASE: TACAN 00101.515 INFO COCKPITBASE: lua state still active TACAN, 51 (status undefined) 00101.515 INFO COCKPITBASE: STALL 00101.515 INFO COCKPITBASE: lua state still active STALL, 52 (status undefined) 00101.515 INFO COCKPITBASE: ILS 00101.515 INFO COCKPITBASE: lua state still active ILS, 53 (status undefined) 00101.515 INFO COCKPITBASE: UHF_RADIO 00101.515 INFO COCKPITBASE: lua state still active UHF_RADIO, 54 00101.515 INFO COCKPITBASE: VHF_AM_RADIO 00101.515 INFO COCKPITBASE: lua state still active VHF_AM_RADIO, 55 00101.515 INFO COCKPITBASE: VHF_FM_RADIO 00101.515 INFO COCKPITBASE: lua state still active VHF_FM_RADIO, 56 00101.515 INFO COCKPITBASE: TISL 00101.515 INFO COCKPITBASE: INTERCOM 00101.515 INFO COCKPITBASE: lua state still active INTERCOM, 58 (status undefined) 00101.515 INFO COCKPITBASE: AAR47 00101.515 INFO COCKPITBASE: RT1720 00101.515 INFO COCKPITBASE: AIRSPEED_INDICATOR 00101.516 INFO COCKPITBASE: AAU34 00101.516 INFO COCKPITBASE: CICU 00101.516 INFO COCKPITBASE: STANDBY_COMPASS 00101.516 INFO COCKPITBASE: PADLOCK 00101.516 INFO COCKPITBASE: AN_APN_194 00101.517 INFO COCKPITBASE: REMOTE_COMPASS 00101.517 INFO COCKPITBASE: KY_58 00101.517 INFO COCKPITBASE: MACROS 00101.517 INFO COCKPITBASE: lua state still active MACROS, 70 (status undefined) 00101.517 INFO COCKPITBASE: AVIONICS_PROXY 00101.517 INFO COCKPITBASE: ACCELEROMETER 00101.517 INFO COCKPITBASE: DVADR 00101.517 INFO COCKPITBASE: 00101.517 INFO COCKPITBASE: MAIN_PANEL 00101.517 INFO COCKPITBASE: ELEC_INTERFACE 00101.517 INFO COCKPITBASE: MFCD_LEFT 00101.517 INFO COCKPITBASE: MFCD_RIGHT 00101.517 INFO COCKPITBASE: CMSP 00101.517 INFO COCKPITBASE: CMSC 00101.517 INFO COCKPITBASE: JAMMERS_INTERFACE 00101.517 INFO COCKPITBASE: AHCP 00101.517 INFO COCKPITBASE: UFC 00101.517 INFO COCKPITBASE: CDU 00101.517 INFO COCKPITBASE: MAVERICK_INTERFACE 00101.517 INFO COCKPITBASE: LITENING_INTERFACE 00101.517 INFO COCKPITBASE: IFFCC 00101.517 INFO COCKPITBASE: DSMS_INTERFACE 00101.517 INFO COCKPITBASE: DATA_TRANSFER_SYSTEM 00101.517 INFO COCKPITBASE: DIGITAL_CLOCK 00101.517 INFO COCKPITBASE: HOTAS 00101.517 INFO COCKPITBASE: EGI 00101.517 INFO COCKPITBASE: HUD 00101.517 INFO COCKPITBASE: DTSAS 00101.517 INFO COCKPITBASE: NAVIGATION_COMPUTER 00101.563 INFO COCKPITBASE: AAP 00101.563 INFO COCKPITBASE: CADC 00101.563 INFO COCKPITBASE: SYS_CONTROLLER 00101.563 INFO COCKPITBASE: PULSE_TIMER 00101.563 INFO COCKPITBASE: TAD 00101.563 INFO COCKPITBASE: VMU 00101.563 INFO COCKPITBASE: TONE_GENERATOR 00101.563 INFO COCKPITBASE: AN_ALR69V 00101.563 INFO COCKPITBASE: AN_ALE40V 00101.563 INFO COCKPITBASE: SIDEWINDER_INTERFACE 00101.563 INFO COCKPITBASE: SADL 00101.563 INFO COCKPITBASE: IAM_INTERFACE 00101.563 INFO COCKPITBASE: HELMET_DEVICE 00101.563 INFO COCKPITBASE: FM_PROXY 00101.563 INFO COCKPITBASE: FUEL_SYSTEM 00101.563 INFO COCKPITBASE: ENGINE_SYSTEM 00101.563 INFO COCKPITBASE: AUTOPILOT 00101.563 INFO COCKPITBASE: CPT_MECH 00101.563 INFO COCKPITBASE: OXYGEN_SYSTEM 00101.563 INFO COCKPITBASE: ENVIRONMENT_SYSTEM 00101.563 INFO COCKPITBASE: HYDRAULIC_SYSTEM 00101.563 INFO COCKPITBASE: IFF 00101.563 INFO COCKPITBASE: HARS 00101.563 INFO COCKPITBASE: HSI 00101.563 INFO COCKPITBASE: NMSP 00101.563 INFO COCKPITBASE: ADI 00101.563 INFO COCKPITBASE: SAI 00101.563 INFO COCKPITBASE: LIGHT_SYSTEM 00101.563 INFO COCKPITBASE: FIRE_SYSTEM 00101.563 INFO COCKPITBASE: TACAN 00101.563 INFO COCKPITBASE: STALL 00101.563 INFO COCKPITBASE: ILS 00101.563 INFO COCKPITBASE: UHF_RADIO 00101.563 INFO COCKPITBASE: VHF_AM_RADIO 00101.563 INFO COCKPITBASE: VHF_FM_RADIO 00101.563 INFO COCKPITBASE: TISL 00101.563 INFO COCKPITBASE: INTERCOM 00101.563 INFO COCKPITBASE: AAR47 00101.563 INFO COCKPITBASE: RT1720 00101.563 INFO COCKPITBASE: AIRSPEED_INDICATOR 00101.563 INFO COCKPITBASE: AAU34 00101.563 INFO COCKPITBASE: CICU 00101.563 INFO COCKPITBASE: STANDBY_COMPASS 00101.563 INFO COCKPITBASE: PADLOCK 00101.563 INFO COCKPITBASE: AN_APN_194 00101.563 INFO COCKPITBASE: REMOTE_COMPASS 00101.563 INFO COCKPITBASE: KY_58 00101.563 INFO COCKPITBASE: MACROS 00101.563 INFO COCKPITBASE: AVIONICS_PROXY 00101.563 INFO COCKPITBASE: ACCELEROMETER 00101.563 INFO COCKPITBASE: DVADR 00101.563 INFO COCKPITBASE: 00101.646 INFO DCS: dbox failed Initialize -7 00101.694 INFO WORLDGENERAL: loaded from mission Scripts/World/birds.lua 00102.021 INFO EDTERRAINGRAPHICS3: Force loading pipeline 'lockon'. Radius 141457.000000. Pos=-356524.125000,13.400333,618382.187500! 00102.194 ERROR DXRENDERER: DXDefTexture: failed to open file land_l2_-25_27.png 00102.800 ERROR DXRENDERER: DXDefTexture: failed to open file land_l2_-25_28.png 00102.810 ERROR DXRENDERER: DXDefTexture: failed to open file land_l2_-25_29.png 00102.892 ERROR DXRENDERER: DXDefTexture: failed to open file land_l2_-25_30.png 00102.900 ERROR DXRENDERER: DXDefTexture: failed to open file land_l2_-25_31.png 00103.499 ERROR DXRENDERER: DXDefTexture: failed to open file land_l2_-25_32.png 00103.508 ERROR DXRENDERER: DXDefTexture: failed to open file land_l2_-25_33.png 00103.631 ERROR DXRENDERER: DXDefTexture: failed to open file land_l2_-25_34.png 00117.237 INFO EDTERRAINGRAPHICS3: force loading finished! 00117.237 INFO EDTERRAINGRAPHICS3: Force loading pipeline 'map'. Radius 28291.400391. Pos=-356524.125000,13.400333,618382.187500! 00117.755 INFO EDTERRAINGRAPHICS3: force loading finished! 00119.463 ERROR DXRENDERER: DXDefTexture: failed to open file land_l2_-25_26.png 00119.829 ERROR DXRENDERER: DXDefTexture: failed to open file land_l2_-25_35.png 00119.868 ERROR DXRENDERER: DXDefTexture: failed to open file land_l2_-25_36.png 00122.570 INFO DXRENDERER: Creating Resource "Unicode" of type 5 00127.295 ERROR DXRENDERER: StretchRect:, D3DERR_INVALIDCALL 00127.300 ERROR DXRENDERER: DXRenderer::SetRenderTarget(posteffecttarget5, 0), Unknown 00238.172 ERROR SOUND: source_is_playing(-1): invalid source 02303.442 WARNING LOG: 17 duplicate message(s) skipped. 02303.442 INFO Config: netview stopped 02303.471 ERROR wInfo: can't open Objects[Vaziani] table 02303.473 ERROR GRAPHICSXP: ModelManager: can't find Vaziani 02303.474 ERROR wInfo: can't open Objects[beslan] table 02303.476 ERROR GRAPHICSXP: ModelManager: can't find Beslan 02303.476 ERROR wInfo: can't open Objects[Miner] table 02303.490 ERROR GRAPHICSXP: ModelManager: can't find Miner 02303.490 ERROR wInfo: can't open Objects[Mozdok] table 02303.493 ERROR GRAPHICSXP: ModelManager: can't find Mozdok 02303.582 INFO EDCORE: (dDispatcher)enterToState_:3 02303.582 INFO EDCORE: (dDispatcher)enterToState_:6 02303.679 INFO SOUND: detaching sdef path ".\scripts\database\coremodules\wwii units\sounds\sdef\" 02303.679 INFO SOUND: detaching sdef path "c:\users\matz\saved games\dcs\sounds\sdef\" 02303.679 INFO SOUND: detaching sdef path "sounds\sdef\" 02303.701 INFO TERRAIN: lSystem::Exit() 02303.701 INFO TERRAIN: lSystem::CleanScenes() === Log closed.