Jump to content

wernst

Members
  • Posts

    365
  • Joined

  • Last visited

Everything posted by wernst

  1. Correct, the real Mossi doesn't have toe brakes. But, it also doesn't have a handbrake lever that simply works as ON / OFF switch. The real Mossi's wheelbrakes are controlled by compressed air. The brake pressure can be gradually controlled by the linear movement of handbrake lever - which unfortunately is not simulated by the digital ON / OFF lever of a TM HOTAS.
  2. Yes, done. I thought I can bind the wheel brakes to one of both toe brakes only. It works far better now as toe brake and rudder input is on the same side (same foot) Good point.
  3. Steering while taxiing the Mossi is challenging, because it's done by differential braking. In order to steer precisely, you need to apply more or less force to the wheel brakes - carefully. Binding the wheel brakes to the pinky lever on my TM Warthog stick is not sensitive at all. Because it only allows digital ON / OFF braking, it is not an analog brake axis. I tried binding the wheel brakes to the analog axis of the right toe brake. The result wasn't great. Steering with both rudder pedals and at the same time carefully apply more or less braking force to only one toe brake often ended in the grass next to the runway. Yes, I know, one answer will be: practice, practice . . . Any other smart tip? (I have the Thrustmaster Hotas Warthog Stick and Throttle, Saitek Pro Flight Rudder Pedals).
  4. That is exactly right. And, one step further: Mount a powerful jet turbine on a piano and install two small flat boards on it as stabilizers - this piano will fly. Unfortunately, it is not possible to steer this beast, but that's irrelevant, right?
  5. Thanks, Bozon. "Never look back" - I like that. The "literal" meaning of this wisdom is a useful tip mainly for start-up. But for the immersion, I love turning valves that I can see directly. On the fuel setting panel there are even more valves, e.g. to the right, the fuel transfer valve, extra oil pressure boost and a some buttons for oil dilution and engine out-cut. I don't want to put all these controls on key bindings. Of course I can also use the hot start, but that's not flying in the DCS world, is it? But thanks again for the metaphorical inspiration.
  6. I'm able to save any snap view from the pilot's seat which is available under key 1. The view of the fuel setting elements is only possible by swapping to the second seat (key 2) and by turning the view 180 degrees. All attempts to save a snap view from this fuel panel view have failed. It's not possible, neither from seat 1 (key 1) nor from seat 2 (key 2). How should I do this? (I don't have TrackIR or any VR item)
  7. Precise calculation of a flight model is essential for a simulation. For this purpose, the interaction between the wings and the air flow must be simulated as precisely as possible in accordance with a given flight model. If the wings are rendered as non-existent, the flight model must not calculate with existing wings. DCS has a pretty good but not always optimal damage model.
  8. I tested whether the simulation makes it possible to launch a Hornet from an aircraft carrier - without the aid of the catapult. Yes, it's a crazy idea but worth a try. The conditions: Hornet on the CVN74 JC Stennis, no wind, carrier speed 22 kts, Temp 20 deg.C / QNH 29.92 No weapons, only built in M61A2 Gun with ammo (1711 lbs) / fuel: 10808 lbs Total take-off weight: 37,606 lbs flaps half, brakes on, full throttle, brakes off Indicated take-off speed at the end of the carrier 146 kts A standard take-off from carrier without catapult seems to be possible when using the full length of the carrier "runway" - in the SIM!
  9. It was the famous DCS Veteran IRONHAND who suggested this special procedure. I've tried his method but apart from a placebo effect in some games after that, I'm now again as far as before. Other than that, any creative idea is welcome, I just hope the devs have them too.
  10. I made the same experience. After all most recent Nvidia driver updates the crashes have gone initially, but only for a short time. I assume that the updates are deleting some graphic settings and memory presets, which will then be "filled" again until the next crashes occur. I'm also at 466.55 and having the same "good old" crashes.
  11. What we know so far: the crashes cannot be reproduced consistently the ED devs obviously have no crashes there are many possible solutions but none last longer than a few days A lot of standard recommendations: OS update, graphics driver update, no mod, no OC, optimize page file settings, clean some folder content and . . . and. . . more excotic ones, but none seems to work truly. confusing OS recommendations: Win10 should be up-to-date, but not too up-to-date, but ultimately only Win 8 comp mode is the most promising workaround for the meantime. The main problem is that any attempt to track down the main fault is made difficult by the fact that the disappearance and appearance of the crash comes completely random in time. It seems that there is a trigger in the program code or in the OS environment which strikes randomly, I call it „trouble trigger“. Perhaps this trouble trigger is not in the program code itself but maybe in Windows 10. The devs may have a particular clean OS which is free from any unwanted trigger. It is their reference system, which is needed for coding in a well known and structured environment. That would explain why the devs did not notice any abnormalities when changing from 2.5.6 to 2.7.xxxx. And it could explain why the Win 8 compatible mode is the best workaround so far as it is free from any DCS injurious triggers. I don't think the devs provided a badly coded 2.7. open beta. Every beta version before was more or less stable, fully usable with only minor cosmetic restrictions, no fatal crashes at all. The devs made the 2.7. open beta in their own, dedicated OS environment, which seems to be a kind of „steril“, which almost nobody of us has.
  12. ok. got it. "Fly" is the button to open the just created empty mission. But what is the point of this "empty mission" procedure step? Does that mean I can load all missions crash free afterwards?
  13. Sorry, I'm a little slow at understanding. I knew how to create and save an empty mission map. But how am I supposed to "Fly" this mission then? Don't I have to bring in any plane into this empty mission via ME later? It would help if I could follow this "solution" step by step. I have the feeling that every single step, no matter how small, is decisive. The devil is in the details.
  14. I'm gradually realizing how crazy your "solution" is but at the same time how effective it might be. I am not a native speaker of English. But now I do understand what an "empty mission" really means. Starting a mission truly empty. Full stop. I'm not asking if this makes any sense, but I'll give it a try . . . really? Is this seriously regarded as a solution? But, after I successfully tried the Win8 compatibility mode, an "empty mission" solution is no crazier either. Why do I think just now back again to the garlic ring around neck solution in this context . . .
  15. ok. before I go a little crazy I wonder what happened that a normal procedure that I've been doing almost forever is now called a "solution". Start a new mission, choose a map, choose an aircraft that, for the sake of simplicity, starts from the RWY. Save the mission. Don't leave the ME, fly around, abort the mission and close the ME. Have a coffee break and then restart the just newly created mission from "my missions". No crash?? What did we discuss here for weeks? Now, no 2nd mission load crash?? Not here!
  16. just to confirm and understand. Creating a new mission from scratch, save it, flying it and close it normally - no crash, ok. But what about loading this newly created mission again next time? Since the first 2.7. update I've done this "standard" procedure of creating new missions many times, with CAU map and different planes. Flying any of these newly created missions right after creation from ME has always been ok, but loading it again was the point. Maybe I didn't understand well what you have proposed.
  17. useful finding. It's worth going on there. I just wonder why we, the beta testers, should not only test the beta and report results but also find out WHY the beta software crashes.
  18. I'm with DCS since 2014. I never ever had any fatal CTD, maybe a handful insignificant software stops - in 7 years. (mainly caused by my mistakes) So far DCS has been proven to be robust and stable, a joy to play. And yes, that's fully true for all previous betas too. Even considering ist open beta, it's now going to be a little crazy. Some say repeatedly and monotonously: update to the latest OS and GPU drivers, others say go back and use the ancient Win 8 mode, and now they say: please don't update to the latest version. I am slowly losing faith that the 2.7 crash problem will be solved in the short term. I bought the HIND and am waiting for 2.7.xxxx stable.
  19. That's what amazes me. Obviously, by jumping from version 2.5.6. to version 2.7. elementary changes are made that should only work with latest W10. That was the plan. Ironically, 2.7 works now only crash free when playing DCS in W8 or W7 comp. mode. Crazy DCS world. I just hope the developers aren't as clueless as I am right now - I bet they are not.
  20. " . . . needs to babysit the software . . ." that's it, you hit the point. If a program only has fewer crashes when I have to apply all sorts of healing recipes, then it's not even in beta.
  21. At first I couldn't believe it and thought: what a crazy idea, the craziest of them all. In addition to 2.5.6. stable I have a second 1TB SSD with 2.7.0.5659 installed, as test system - which had multiple crashes, regardless of applying any of the multiple cure recommendations. Just for fun (what I thought initially) I recently started 2.7. in W8 comp. mode (64 bit, admin). I tried all possible "painful" startup options without implementing any of the many recommendations. Success . . . . no single crash for 2 days so far. Now I'm not only speechless but wondering what's going on here. Everyone from DCS strongly recommends installing the very latest updates for Win 10 and relevant graphics drivers, and then that. I don't know what else to do but I think it is worth investigating this "miracle" further. I would ask myself: What is different in W8 to W10 considering what is different from 2.5.6. to 2.7.xxxx EDIT: Please note: The "I'm running DCS in W8 / W7 comp. mode" idea is not mine. It has been reported here by various members.
  22. I like that good sense of humor. It makes the annoying crashes a little easier. I will also try your recipe with a garlic ring around my neck. But since we neither have a full moon nor can I see the moon, I will be flying in Win XP compatible mode.
  23. No way, I don't do that. I enjoy DCS 2.5.6. stable (in my case 100 % crash free so far) I enjoy the good things of DCS, even without spectacular clouds. When I read what recipes are suggested here to avoid crashes, I get even more gray hair . . . while I'm still alive. (btw, I have 2.7. on a second drive for test purpose and follow up)
  24. Did you have the "2nd load crash" before you switched to W7 comp mode?
×
×
  • Create New...