Captain Orso

I have this problem too, and I've had Save View checked for like forever. BTW I'm in VR, so maybe that plays a role too, but when I start Oculus home I ALWAYS center everything before starting DCS. Also, since about a couple of weeks, sometimes when getting into the A-10C cockpit the first time in a mission, my view is pressed with my nose against the instrument panel. I have to use <NUM-/> to move way back to get a normal view.

Thanks for the reply Tholozor! I've been turing and waiting for the Deedle-Deedle report at Off-Right and Off-Both and realized that it might be just a waste of time if you're in a hurry.

... um, Bleed Air Select Switch. How slowly must you -- or how fast may you -- turn the Bleed Air Select Switch at start-up for it to work properly?

LOL thanks for the extended explanation. You are above and beyond I'm only saying that the coding of 'default.lua' is... easy to misinterpret.

I requested this myself once what seems ages ago. I'd like it for exactly the same reasons. It would be an awesome boon to making videos. So sad that the others who replied were so caught up in their own business that they couldn't even address OP's subject other than to say, "I'd rather..." or to rant like he didn't even read OP's post.

Thanks for the reply. Clicking the switch in-cockpit confirm your statement. Odd the way 'default.lua' is written, but what the heck.

They are included with the installation. Look under Static Objects -> Category: Ground vehicles -> *AM2FIELD HIDE and *AM2FIELD HIDE SMALL

You can download both the modern and WWII mats from here: https://we.tl/t-HVfoguD9hO ... for the time being. SUN said one one should be used at a time IIRC.

This is exactly what I did, using <Paddle> as the modifier. The only issue I have is that when I want to "talk" to ATC or AWACS and press <Paddle><Mic-Fwd> SRS only registers <Mic-Fwd> and although the radio menu still opens normally, it accompanied by that radio's mic being clicked on and off in SRS. It's not a big deal, but it would still be nice if it didn't do that. Anyone have a idea on how to fix that?

I'm using the TM Warthog Throttle Mic Switch Push (DX 2) as a Modifier named <Thumb-Press> I'm using the TM Warthog Stick Paddle (DX 4) as a modifier too, named <Paddle>. Because I still want the functionality if the Paddle for NWS Disengage etc., I've assigned it to the Master Mode Control Button (DX5). In CONTROLS -> F/A-18 Sim <Paddle><Master Mode Ctrl Btn> is assigned to TakeOff Trim, and <Thumb-Press><Master Mode Ctrl Btn> assigned to Trim Reset. When category 'ALL' is selected, both <Paddle><Master Mode Ctrl Btn> and <Thumb-Press><Master Mode Ctrl Btn> jump directly to their assignments. In-Game <Paddle><Master Mode Ctrl Btn> works as expected. In-Game <Thumb-Press><Master Mode Ctrl Btn> acts as if <Thumb-Press> were not being pressed. In the cockpit you can see the paddle on the back of the stick being pressed. If I assign <LCtrl><Master Mode Ctrl Btn> to Trim Reset it works. I can use <Thumb-Press> as a modifier for other assignments, and they work fine, just this combination seems to be bugged.

These are the pertinent lines in the 'default.lua' file: { down = cpt_commands.CanopySwitchOpen, up = cpt_commands.CanopySwitchOpen, cockpit_device_id = devices.CPT_MECHANICS, value_down = 1.0, value_up = 0.0, name = _('Canopy Control Switch - OPEN'), category = {_('Right Wall'), _('Systems')}}, { down = cpt_commands.CanopySwitchClose, cockpit_device_id = devices.CPT_MECHANICS, value_down = 0.0, name = _('Canopy Control Switch - HOLD'), category = {_('Right Wall'), _('Systems')}}, { down = cpt_commands.CanopySwitchClose, up = cpt_commands.CanopySwitchClose, cockpit_device_id = devices.CPT_MECHANICS, value_down = -1.0, value_up = 0.0, name = _('Canopy Control Switch - CLOSE'), category = {_('Right Wall'), _('Systems')}}, The 'CLOSE' line uses 'value_up = 0.0' on 'cpt_commands.CanopySwitchClose' so that when you press and then release the 'CLOSE' button, the canopy stops closing on releasing the button press, which is exactly what can be observed. The 'OPEN' line also uses 'value_up = 0.0', but on 'cpt_commands.CanopySwitchOpen'. When you release pressing the 'OPEN' button the canopy begins to open, but when release the 'OPEN' button the canopy continues to open until you press 'OPEN' again, or 'HOLD'. Obviously since 'OPEN' and 'CLOSE' are written using the exact same format, they are intended to work exactly the same; but the do not. The 'value_up = 0.0' parameter of the 'OPEN' line is NOT working as intended, it is doing nothing and could as well not be there. It's a very minor bug, but there it is.

This is a very minor bug. [bug] Assign Canopy Open to an On/Off switch. Assert switch and the canopy starts opening. Release switch and the canopy continues to open. Reassert switch and the canopy stops opening. Assert switch again and the canopy starts opening again, etc. etc. [WAD] Assign Canopy Close to an On/Off switch. Assert switch and the canopy starts closing. Release switch and the canopy stops opening.

Maybe it is a bit overboard to say the module is sloppy, but I cannot understand the mentality to neglect something like elevator trim when at ever single air-start it slaps the player in the face to say, 'we don't care how much this taints your experience every time you air-start'. I just don't get it.

Ahhh yes... I need to fix my HOTAS kneeboard chart; still too unclear. Okay, Prof3 removes the SOI indicator dot, I saw that clearly. Why TMS Forward Long then at times doesn't set the SPI is still a mystery to me. I will have to keep my eye on it and see of I recognize something. I do note that is some circumstances the HMCS overlay seems to slide out of position so that already set SPI's are WAY off target. On the TAD they are good, and in the TGP also IIRC, but in the HMCS way off. Maybe that's part of what I've seen, that the SPI is actually placed, but the HMCS doesn't show it where I expect it to, and I just didn't find the display, because it wasn't where it ought to be.

Ummm... how do you declutter the HMCS?

When everything is fresh and new, coolie-hat up makes HUD SOI and the SOI-indicating asterisk appears on the left side of the HUD. Coolie-hat down makes HMCS SOI and the SOI-indicating dot appears on the left side of the HMCS display area. 1. Make TGP SOI and then press coolie-hat down to make HMCS SOI. The SOI-indicating dot does not appear, but TGP is no longer SOI (frame around MPCD is gone and no where else is there a SOI indicator). 2. Coolie-hat up makes the HUD SOI agin, and the SOI-indicating asterisk appears. 3. Coolie-hat down and the asterisk disappears, but the dot does not appear on the HMCS. You can also not use TMS forward long to set SPI for the HMCD. This is reproducable.

Thanks for the answer ARt-J :thumbup: To paraphrase... someone... 'hmmm'. I guess I've just been spoiled by the P-51 and the Spitfire and now have to live with more sloppy modules :(

So, I'm quite new to the Bf-109, but I've flown the P-51D and Spitfire for years and have many hours in each. It seems that no matter how slow I start the Bf-109 in the ME, when clicking the [FLY] button, the 109 immediately starts to buck like and SOB and only calms down when I add nose-down trim. Again, whether starting at 400 kmh or 200 kmh, the results is the same -- just at 400 kmh the bucking is more pronounced. Is this normal?

When doing an airstart at 22,000 feet, oxygen is not turned on automatically. In the P-51 and the Spitfire, regardless of the altitude, oxygen is always turned on during an airstart.

I have a mission on the Normandy map I've used for years to do gunnery, bomb, and rocket practice. It is now no longer working. I get the messages when the MIST and rangescript lua files are loaded, but when I fly into the strafe zone, no message greets me, and when I hit the strafe target, only damage is reported.

Read the README.md file. It says, "Copy the Scripts folder into your DCS Saved games folder". That means also all of its contents, and not just A lua file. Once scratchpad is properly installed, you can set the hotkey to whatever you wish, and of course you can configure VoiceAttack to 'press' the hotkeys you have set.

With the MAV as SOI, TMS Aft Short (Ground Stabilize) the crosshair, if they have a valid aim-point on the ground, the crosshairs lock to that point. However, as soon as you start to slew the crosshairs, they become unstabilized and follow the movement of the airframe instead of being stabilized to the ground. You can still slew the crosshair, but their movement is relative to the airframe, and not the ground. EDIT: Oops, this should have been posted to the Bugs sub-forum, sorry :doh:

Scratchpad is not an independent app which you start on it's own. It is scripts hooked into the DCS environment so that when DCS starts, it also loads the scratchpad scripts and runs those along with DCS'es scripts. Therefore, you cannot shutdown scratchpad, you can only close the overlay-window. It's still running so-to-say, albeit with nothing to do. You can just as well quit your mission and stop DCS without closing the scratchpad window. It's all the same.

No, you must stop DCS. In-Game Scratchpad is based on scripts, which are hooked into DCS run by it. You cannot start nor stop In-Game Scratchpad independent of DCS, and as far as I have seen, DCS only updates the Scratchpad files when DCS itself is shutdown. Opening and closing the scratchpad window is only that. It's like minimizing and restoring a windows app.

Yes! All the pages you create and update in In-Game ScratchPad™ are saved on exit into 'c:\Users\user_name\Saved Games\DCS{.openbeta}\Scratchpad\'. The first page is '0001.txt' with subsequent pages being '0002.txt', 0003.txt' etc. While DCS is not running, you may copy, move, and edit them as you wish (I recommend using 'Notepad++' as the default text editor) -- I'm not sure what happens if there is no '0001.txt' present in the Scratchpad folder when starting DCS -- which starts the In-Game Scratchpad™ scripts, but you can try it to find out -- you probably won't be injured too badly... ;) I use this fact to implement map specific pages, depending on where I am flying. So for example I have one page with the coordinates of Persian Gulf airfields I find important. If I'm going to fly in a PG mission, I simply slip that page into the Scratchpad folder and adjust the names as required. You can think of it as a kind of quick-kneeboard-extension.