

-0303-
Members-
Posts
849 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by -0303-
-
'Instant search' doesn't seem to be a thing currently. Searching "about:config" it turns up the same result as something nonsensical like "ffffffffff". It had to be "added" and then I set it true and false with no difference. Hit the garbage can symbol to remove it again. Testing Edge and Chrome very quickly and cursory (not logged in) both seem to work as they "should", i.e. always going to the top clicking PREV or NEXT. How many how this problem not using Firefox except Rayrayblues?
-
Firefox 109. 1. Emoji's work as they always have, a little slow loading but they work. 2. The setting including "Take me to comments I haven't read" is obviously a different matter, a setting just for entering a thread.After entering a thread clicking NEXT or PREV should always go to the top. Arguably PREV could go to the bottom "going backwards" but I've never seen any forum work like that. 3. I tried Firefox "SAFE MODE" no extensions, private mode (logged out) and logged in. In all cases it works the same, sometimes it goes to the top, sometimes the bottom, sometimes somewhere mid page. Most of the time it goes to the bottom. 4. Clicking a page number (from already inside thread) seems to work the same, ie randomly but mostly bottom. I have a hunch. Maybe the browser goes back to the remembered scrolled status the last time it was on that specific page. Most of the time I leave a page I'm at bottom (having read/scrolled all the way down).I seem to have a better shot going to the top in threads I've never been, like discussions of some terrain I don't have. How to test that? Wiping every cookie?
-
Game Options. Game avionics mode removed. I never understood why anyone would do "game mode". I imagined it a drain on ED resources to keep supporting.
-
Normandie. Wolfpack most likely. Not Spartan. Increasingly convinced it was a drone. F10 view probably not in view (inland, not coast). Visual damage may or may not correspond to actual.
-
Artificial horizon doesn't work correctly on a single airplane AFAIK. I and others have tested a dozen or more planes. There's an exhaustive thread on this since April 20, 2021. It boils down to the pendulous vanes function is never implemented or bugged. Seems this bug was and is copied to every new plane (like the Mosquito). Artificial Horizon is part of the "sixpack", the six basic flight instruments. Was gearing up for a yearly anniversary bump to that thread. Got an acknowledgement of this for the Spitfire and have waited for this to be addressed (for Spitfire and every other plane).
-
Weirdly not getting authorized first attempt (no modules). Seems to have worked 2nd attempt but it hanged minute at ~"getting authorized". Never seen that before. Successfully logged into Multiplayer (Hoggit training server), so that works.
-
Clicking on the FPS counter opens an blinking cursor and the FPScounter cannot be RCtrl+Pause dismissed until clicked outside. Feature or bug?
-
Don't go under 200 knots ... Not me. Just saw Dora loose wing (just outside gear) colliding Spitfire and happily fly on. On second thought took out the video. Real person may not like being publicized. A valiant attempt at landing. Lost control just after gear out and getting slower than 200 knots.
-
@MAXsenna Actually ... having functional "clickable cockpit" is such a huge plus I'm not sure I would go back if I could (*1). I mainly wrote this to describe the (now inaccessible) Microsoft Windows "stretching" function that no one has talked about in any ALT ENTER thread. Seemed to me that was the actual thing removed when discussing ALT ENTER. ~ Addendum. I remembered why "I find myself running windowed a lot". It's inconvenient to not be able to quickly use programs outside DCS (or at the same time). Besides arguing on internet, checking Blue flag map, there's SRS radio, Teamspeak, adjusting Headtrack. *1) Note, clickable cockpit was always available when not using the "stretch" thing and I knew that. I just explored and reevaluated a bit more since ALT ENTER was removed.
-
This is what happens. So much confusion about this. DCS has removed a Windows functionality. My experience, what I must do now to have a "full screen": My setup is similar as Commander2. A laptop and an external screen (native 1920x1080 16/9). Note, no VR for me, only discussing screens. Microsoft has not changed anything (this is proved by downgrading to Sep.2 version) . DCS has removed the Microsoft ALT ENTER functionality from DCS. What is the "Microsoft ALT ENTER functionality"? Some describe it as "maximizing". It "stretches" an MS window to full screen borderless. It does NOT change the actual resolution, it just "stretches" the window (*1). Having a weak laptop I used that all the time. I used to set DCS resolution to lowest possible and then I could quickly ALT ENTER between the small DCS window (1280x768) to stretch and fill the whole 1920x1080 screen or back to the native "true" 1920x1080 MS desktop. This doesn't work anymore. ~ Now I must check the "Full screen" checkbox and I set DCS resolution to 1366x768 (the lowest which is also 16/9 ratio). To switch I can ALT TAB. Alternatively I can click on my laptop screen to get back to Windows desktop 1920x1080. From Windows desktop I can click on the taskbar DCS icon to get to DCS (it switches screen res. to 1366x768). Switching either direction takes about 6 seconds. With "Full screen" checkbox checked I can not access DCS and Windows desktop at the same time. Often browser windows now gets shuffled to the small laptop screen and I must drag them back, which is a small annoyance. Besides that, my problems is mainly due to having a weak machine, so I'm not sure I can complain too loudly. I find myself running windowed a lot so I can watch DCS logging in while using the normal desktop. I might change that habit. I had the notion on starting to write this I sometimes had to wait minutes locked in waiting for DCS but I failed to provoke it. CORRECTION: I just had to browse in 1366x768 resolution (while editing this) for a minute while waiting for DCS to "exit to desktop" before it switched back to 1920x1080 again (of course with a stronger machine I would just run 1920x1080 native all the time and never switch res.). ~ *1) A significant drawback of the "stretched" mode was that clickable cockpit gets disoriented and non functional. For a short time a few years ago, DCS had a fix that had clickable cockpit working while stretched, and then it went away with another patch.
-
I did that. Ca 1998. A game called "Warbirds". Once or twice a month there were multi hour "scenarios". Reenactments of Europe or Pacific historic missions. The most looked forward to and popular events. But things were different. It was a tight nit community. Everybody posted to the same forum. DCS is much more splintered. During the long "dead times" everybody text chatted on a common channel. Half the entertainment was the chatting. Late summer: "It's an August Event". Game was arcadish. Admittedly gunner positions were seldom all filled, though that happened but most were in fighters. Between 30 - 200 people showed up. There would be too few bombers if all gunner positions were filled so choice was almost always, less gunners, more bombers. The bombers typically only had pilots except for one or two persons who wanted to be gunners. A few scenarios scripted that bombers must have gunners. I took part in an all bombers must have all gunners mission maybe half a dozen times over three years. Very useful, player could teleport between positions. From pilot to rear gunner for example. This is required for game play because it will seldom to never be enough people. I think it would be a huge investment for DCS to develop a bombers with all positions. Not one but 10 different "clickable" cockpits. It would be an expensive module. Some of the faithful would buy it. It would not be used very often. An active enthusiastic forum for discussing Missions / Scenarios to would be needed if it were to be used with any regularity. Just a thread in "Western Europe" forum would not be enough.
-
A Windows command. Didn't know that. But the current Win 10 environment Windows 10 Home Version 21H2 OS Build 19044.2006 does respond to ALT ENTER using the September 2 Open Beta. So the current Windows environment does not prevent ALT ENTER usage.
-
I'll point out that reverting to a working Sep. 2 Open Beta version and going back to non working latest version on the same machine within half an hour means it's not likely not Microsoft's fault. Or, if they changed something, it's fixable.
-
This is NOT solved. Hitting ALT ENTER nothing happens. This severely inconveniences how I run DCS. Having a weak machine I run lowest possible resolution (1280x768). I toggle between windowed (inside 1920x1080) and stretching to full screen with ALT ENTER. Windowed mode gives me easy access to whatever I do outside DCS while DCs still running. Browsing, adjusting head tracking, arguing in the forums ... For testing purposes I reverted to the Sep. 2 2022 version using: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin>DCS_Updater.exe update 2.7.17.29493@openbeta I let it create a pristine DCS.openbeta folder in Saved Games just to be sure of no confusion. Later went back by just accepting "wanna update to latest?" (I had renamed my DCS.openbeta so I wouldn't lose any settings) . Sep. 2 version works as it used to. I can toggle back and forth with ALT ENTER. Edit: ALT ENTER is a Windows command. It was never a DCS command. I also reverted to Sep. 2 to find the OPTION name for ALT ENTER in the OPTIONS screen in case the name had changed. Turns out there isn't a name (is there?). ALT ENTER is captured and reacted too whether I'm in the OPTIONS screen or "flying" screen. Neither could I find anything searching for "Screen" in either plane mode (example P-51D Real), UI Layer or General. Just found Screenshot. If the option has a mappable name it's not accessible from the OPTIONS screen . Note, whatever it means: In both old sep. 2 version and latest version there are asterisks next to Vsync and Full Screen. Ie for both functioning old version and non functioning latest version . So the asterisks signify nothing regarding this. Though in an old screenshot from February 2019 neither have asterisks. I've never checked/enabled either.
-
Skyraider. Being more than anything into piston tail draggers, especially carrier planes, that is welcome. Not quite WW2, but close enough. Love to see the ultimate technology development for this genre. Maybe that would be the last Griffin Seafire. The exterior looked a little crude but that will improve? Developer access to two airworthy "Spads", that's promising. Of course Skyraider has a long career. Korea, Suez, Vietnam (even Algeria says Wiki).
-
I don't get it? I've always done multiple engine starts in a single mission I fly, land, shut off engine, restart and take off again (with or without repair). I did that just now (auto and manual). DCS does not and is not programmed to prevent us from abusing the engine (or the electric starter) if that is what you're thinking about. Why would the real thing differentiate between a less than a second starter push and a multiple second push?
- 13 replies
-
It's not a DCS scripted mission. It's a single Spitfire placed in Batumi as "Takeoff from ramp" as opposed "Takeoff from runway" for example. Can rename the track file "Spitfire manual start fail" to .miz extension to get the mission file I believe. Could be correct behavior. Does a circuit burn out from a short touch? Not impossible I guess but does it make sense?
- 13 replies
-
I've edited the title to be very specific. I also edited the top post language to be more specific. I'm only talking about the electric starter, not the whole starting sequence. This because my bug is different from LeCuvier's. This bug is avoidable if knowing about it. It is also 100% repeatable (and as such should be "easy" debuggable). Still curious if the track works the same for others? Meaning starter engine turns at first press and then doesn't at subsequent presses. Also. Years ago (and still for all I know), sometimes, after repair, the starter does not turn the engine over. Adding "ground power" (assuming empty battery) made no difference. Posted about that years ago but it was unresolved. Maybe because it was hard to reliably repeat and make a track. Anyway, this new bug, also starter refusing to turn engine over,might be directly related to this old bug. With luck it could fix both. Soo, self inflicted?
- 13 replies