-0303-

I was bored ... and I find the taxiing can be problematic in tight spaces, especially if it doesn't act as expected.

Did a mix tape of relevant free castoring nose wheels. 00:00 C-101C Not great 00:12 L-39C Nearly perfect 00:22 Mig-15bis Perfect 00:39 Mig-19P Nearly perfect 00:58 Mig-21bis Semi good 01:10 Mig-21bis Bad 01:29 Yak-52 Perfect

I just experienced just this on Caucasus Aerobatics Online Server (winter time). All three things including the ~200. It happened after 30 minutes maybe. Pitot was on all the time.

The mechanical clocks technology I believe has been the same since before WW2. ASI, VSI, ALT, all three depends on air pressure changes. They all have in common a "static pressure" input that affects all three. If ED actually models a frozen static pressure input, that would be ambitious and interesting. If pitot froze it would only impact the ASI, not the VSI or ALT.

I found assigning the left side 3-pos TM throttle switch yields up / takeoff / landing settings which is quite convenient. Usually one only gets 3-positions with fancy lua file editing. It's usually just up / down & nothing in the middle. Often I look for a "Next/Previous" choice because it's the easiest.

-Locked left wheel. -Powered up slightly, to make the castor turned maximally and stopped. -Unlocked left wheel. - Powered up again: watch video. It's not a super market trolley (castoring wheel) but this looks wrong (IMO). Shouldn't it straighten out immediately (and then weakly turn left)? I can imagine damping being built into the castoring but this looks and acts (not just cosmetic) like its rusted nearly stuck.

Painfully remove bit by bit until finding what it is ... Yikes. Know the routine though. Maybe I'll try something next time. A question that seem more fruitful. Embedding snapviews is a feature (supposedly). Someone somewhere knows how to trigger it, should have documented it. How to avoid it.

Always from scratch. For that reason, from scratch to avoid copying "bugs". They're very simple. I set spawns for a dozen different planes, experimenting with takeoffs, landings, winds and weather. Would be a real pain if I actually tried to do big missions.

Came here to report DCS crashing (CTD) using Auto Start (LWin Home) for M-2000C. Verified in a clean install. Two things. -Latest patch is "2.5.6.60966 Open Beta" not "2.5.6.60996". -The hotfix, I'm just copying that into the main folder ("C:\Program Files\Eagle Dynamics\DCS World OpenBeta")?

So ... happened twice again. I wish I knew what action causes "now I'm gonna save default snapviews and only these will be usable for the mission". So I used 7-zip twice again to remove the config and track (and track_data). Why is it happening so frequently now when I haven't encountered it for literally more than a year? I can see the point of customized snapviews for specific miz files (kind of, but NOT arguing for any resources spent on this). But then they should be editable. I only ever seen the default views, so what's the point? And how do you create them?

I thought I found it. Made a video and all. Bug appeared after repair a few times. And then it didn't, so no consistency. Just one observation. The rear most throttle position is required for engine to be startable. I noted that Auto Start Script does retard throttle rear most. Also it can be bound to a HOTAS button to make it go rear most position. Observation: After bug appears, neither Auto Start script or bound HOTAS button makes it go to rear most position. What to think of that? Software bug, nothing to do with joystick calibration (as some thread suggested). Using bound HOTAS detent to go rear most and forth. Illustrates where throttle must go to make engine startable. While experimenting I encountered two semi amusing "bugs". To damage for a repair I pancaked. Wheels still up after repair. Undamaged, sitting on the belly ... Hard landing to break gear but keep them out. After repair, gear just crumbled. On belly again... Is this bug around since 2015?

Tried freeflight Yak-52. No, it doesn't toggle.

Thanks Rudel, Happily I didn't delete, just renamed Saved Games (was going to harvest snapviews settings). I deleted Config and Track folders (using "7-zip"). Seems to have worked. I know a very similar if not identical problem exists for some Instant Action missions (separate snapviews saved with the mission causing trouble). Maybe I should have remembered that. I don't fully get it yet, but I expect it'll get into focus ... eventually. *I* created all the files. What I don't get is at what point did it decide to place default snapviews in the miz file? When I save miz file in Mission Editor to go to flight mode? It seem to pattern with "new" planes I hadn't flow before or not in a long while (meaning I had not done any snapview saving before saving miz file). ~~~ Wonder more folders / files I can delete to save space (Track_data?) mission, theatre, options, scripts sounds like required files. Files that exist (after deleting Config and Track folders):

... and snapviews doesn't stick offline again. miz file #3 corrupts. Created caucasus4.miz that works but for how long? I give up. Delete Saved Games and start over.

It did not jump with 2.5.5. On the other hand 2.5.5 was not clickable cockpit. No going back there. Obviously I'd prefer clickable cockpit to work. It's fixable if DCS choses to prioritize resources for it.

This is wrong. Ailerons are always fully hydraulically controlled. Also, because of this, any notion of the stick "getting heavy", to the extent suggested (if suggested) in this thread is completely wrong. Fact is, as the manual explicitly says (in multiple places), "aerodynamic loads of any kind cannot reach the pilot through the stick". It says further "an artificial-feel system is built into the aileron and horizontal tail control systems to provide normal stick feel". Amusingly perhaps, the F-86F stick functions just like your desktop TM WarThog (if spring center was adjustable as "trim"). The pilot moves the stick and hydraulic sensors out in the wings adjusts ailerons accordingly (detailed pictures of the mechanism are in the maintenance manual). Any and all stick forces are adjusted on the ground. Find all F-86F documents uploaded here by drPhibes. F-86F Flt Manual + perf data page 1-31 (pdf 41) Maintenance procedure to adjust stick movements to within tolerances, make sure left and right are symmetrical. Point 18 suggests 30 pound at "center of the stick grip". These pics illustrates how the mechanics works. Maintenance page 76 Figure 2-16 Adjusting Aileron Control System and Aileron Feel and Trim System (Sheet 1 of 2) page 76 (pdf 82) Maintenance page 77 Figure 2-16 Adjusting Aileron Control System and Aileron Feel and Trim System (Sheet 2 of 2) page 76 (pdf 83) Yes, I do find F-86F behavior "weird" above 0.93, without having tried to analyze it. If historical sources says controllable above Mach 1, I'm all for that. But take note of how the stick functions.

Lua files are plan text files. Any text editor, including notepad will do. No reason NotePad can't save files. NotePad++ is a far better, more advanced and free editor though. As easy to use as Notepad. NotePad++ recognizes a great number of source codes including lua and will helpfully color code the syntax making it easier to read (comments are green etc...). To open any file with anything (more or less successful) use Win 10 rightclick "Open with". Better, associate file type lua with text editor of choice. Again NotePad++ is very good. Rightclick on lua file -> Properties - > Change. Scroll down, NotePad++ will be in the list if installed.

.... and it happened again. I had chucked my old "corrupt" miz file and created a new one. And now again, snapviews doesn't stick after new spawn on my new miz file either. (Note, neither miz file were anything special, just a small file with a dozen different plane spawns to experiment with takeoffs landings, wind conditions etc ...) I really don't want to redo the entire SAVED GAMES folder but it seems I'll have too after all, to get rid of this bug wherever it is. Snapviews saves but does NOT show while in my newly created replacement miz file. Snapviews DOES save and show when I go online multiplayer. Last attempt. Created caucasus3.miz (after caucasus.miz & caucasus2.miz quickly went corrupt). Seems snapviews are saving again. For how long? Why does two files corrupts within weeks when it last it happened was ~1.5 years ago? Unless something is corrupt outside just the miz file. ~1.5 years ago I chucked all of SAVED GAMES. Attached file, not purged to single plane (unlike above). corrupt Caucasus2.miz Noticed it starts a replay if "opened". Disregard, load mission in started game, spawn any plane and try to save snapviews.

I've decided to go crazy with forum tags (tagging) Created new thread.

Tags can be very useful. I've decided to go crazy with tags. Even if I'm the only one that tags and it only helps myself finding my own posts, that's well worth it. I'd tried to be thoughtful about tags. Tags I invented (or will, given the opportunity). Categories: 1) Obviously (certain) tags should correspond exactly to the terms used in game (and/or Mission Editor). Example exact vehicle tags: "p-51d-25-na", "p-51d-30-na", "spitfire lf mk. ix", "spitfire lf mk. ix cw", "cv 1143.5 admiral kuznetsov(2017)", "cv 1143.5 admiral kuznetsov". Example other in game exact tags (I created) "Adjust Controls", "Controls indicators". 2) Variantless top plane category tags are abbreviations of the full tag. Example: "p-51", "spitfire", "fw 190". Not expecting a P-51B or P-51C any time soon but if so, they're included in the top variantless category... 3) Generic (not necessarily existing in game) useful well named(?) tags: "fullscreen", "auto start", "auto stop", "bug", "bug report", "cowl flaps", "menus", "cursor". I created "miz file" and "trk file", taken from file extensions. File is attached or discussed. Tag I will probably create soon "lua file". Exact naming "auto start", "auto stop" exists in some plane controls but are named differently in others. So I liked these as generic for every planes "LWin/RWin Home" & "LWin/RWin End" command. I made the assumption spaces within tags are fine (though I can see reasons for why not depending forum tag implementation). Forum admin may want to consider a tag policy. Advanced ideas: Suggest while typing in advanced search Possibly "easy" doable: Existing tags are recognized & suggested now when adding tags in a new thread. This mechanism should work the same when typing tags in advanced search. Better still, tags should be listed in order of incidence. This will inform of which tags actually exists and which tags are most used (relevant). Typing "spit" suggests: spitfire 206 spitfire lf mk. ix 127 spitfire lf mk. ix cw 99 List all tags window (advanced search) Might be "easy" doable. Make (activate?) alphabetical window listing all tags clickable. Create and vote on tag relevance at each topic start Nobody, no admin, wants to police tagging. I don't know what to do about that except maybe a system where users can upvote and downvote each tags relevance at each topic start. Users could also create new tags even if they're not topic starters. Tags gets deleted on zero / negative relevance. This could weed out "bad" tags without need for admin intervention. Highest vote count tags list most relevant tags first at each topic start. Example, if discussing Spitfire, abbreviation tag "spitfire" (or exact tag "spitfire lf mk. ix") should get most votes and get listed first. Actual tags from bug report I did but with imagined tag listing and imagined tag relevance counts. Imagine buttons to the right for tag relevance upvote/downvote bug report 11 i-16 9 repair 8 reload 8 landing light torches 4 Note, "relevance" refer to up / down voted tag relevance within each topic (overall forum incidence of specific tags is a separate thing, incidence of "spitfire" tag could be 206 while relevance inside any individual topic thread much lower). Tags synonymizing More advanced: Tags synonymizing: "auto start" "auto start" "engine start" (two latter exist in game), typing one in search includes all other. Ed/add changed "autostart", "autostop" to "auto start" & "auto stop" in the name of exact naming, because multiple planes uses that.

Must click twice in fullscreen when game resolution differs from monitor resolution. Still here 1 year on. Figured how to capture cursor, new gif. DCS 2.5.6.60720 Open Beta For greater production values, see below

All seems fixed now with DCS 2.5.6.60645 Open Beta patch. Distance & direction fixed. Quick look elevation and N E position seems fixed too.

Update 2, not bug, Snapviews embedded in miz file, see reply #3 Rudel Update, file corrupted again, see next post below. Apparently miz file can be corrupted to only show the default snapviews. Manifests as: Snapviews saves and works while in mission but next spawn, back to default snapviews. But, saving snapviews while inside corrupted miz file mission does show up on running non-corrupt miz file mission or running multiplayer. So bug seems restricted to inside specific corrupted miz file. I (vaguely) remembered it was the miz file years ago. Then, I nuked Saved Games folder. Not this time, just deleted corrupt miz file. Time will tell if this is it. Attached corrupted miz file (single Mig-29 on ramp). Test: Save snapviews, Quit, respawn and notice default snapviews. Same thing may have happened to other player, "Snap View doesnt saves" Obviously ensured clean install, fresh Saved Games folder (to which I imported old corrupted miz file for testing). Created "miz file" tag (will/would create "lua file" and "trk file" tags given opportunity). corrupt Caucasus.miz Very rare bug. Except maybe if someone built a large miz file without previous version backups and have to chuck all of it.Still rare though. ~ Going crazy with tagging: created "trk file" in old topic (deleted/replaced "attached track", indicates trk file attached or discussed). Will probably create "lua file" tag in old topic. Systematic symmetry trk miz lua...

Yeah, there's a zero knot "CV 1143.5 Admiral Kuznetsov" in the river next to Batumi that traps fine (aerobatic online caucasus server). Updated tags to exactly how they appear in Mission Editor and in game "cv 1143.5 admiral kuznetsov" & "cv 1143.5 admiral kuznetsov(2017)"

Don't have Supercarrier (SC). Kuznetsov(2017) ONLINE (SC version apparently) is used in Aerobatics Online Caucasus. Used Kuznetsov OFFLINE. So (SC) Kuznetsov(2017) seems untrappable OFFLINE as well (so is Abe Lincoln). So I must have SC to be able to trap Kuznetsov(2017) or any SC. Su-33 can only trap Stennis or non SC Kuznetsov.