yngvef

It proves my point that fanboys are the biggest threat to DCS... And you did it again. Well done.

Continously whining? Keeping the bug report alive is essential when we are dealing with a dev that almost never checks the forums. This report is 2 weeks old. If it hadn't been constantly bumped, it would be way down on page 3-4... and then it would NEVER be seen. The fact that you get all snarky just proves my point.

People think the critics are the biggest threat to DCS. I say it's the fanboys who are completely blind to any criticism and even pretends that CTD bugs are "minor", even though the devs have not even responded to the report in two weeks. Heatblur is completely in-active on the forums when it comes to a lot of bug reports, and considering this is an early access module, they should actively engage with the community. After all, we are helping test the module. But what help is it to test and find faults when the devs (seemingly) don't listen and the fanboys are trying to silence the bug reports? The fact that ANY bug thread can linger at the top of the forum for two weeks without any attention is not good enough. I don't expect everything to be fixed instantly, but a short message or update letting us know that it is a known bug isn't too much to ask. Even an edit of the thread title to [Reported] would at least show that they've seen it (as I've reiterated many times) Heatblur has made a great module with the F-14, but it is certainly not finished yet, and I will continue to report bugs as I still believe they should be helpful to the devs. And whether or not it's a gamestopper, I was talking literally: it stops the game, as in it's the kind of bug that makes the game stop. Can you still play the F-14, yes, but nobody can claim it's ideal that we have buttons in the cockpit that will quit DCS.

I'm confused. Is anyone actually defending a CTD? Or do they think they are defending Heatblur by saying a CTD is not a bug?

Yeah, but this thread has been at the top or near the top of the bug report sub-forum for two weeks now. And it's a fairly big thread about an actual CTD bug, that should bring attention immediately. I mean, we're not talking about a temperature sensor being slightly off, or a texture glitch, but an actual game stopper. What it means is that I currently have a button mapped to my throttle that will instantly crash the game, every time! I would expect some kind of response. At the very least: "we are aware, we are looking into it." or something. As it stands now, we have no idea if this is even being worked on.

I am also wondering why there is no response from Heatblur on this. Are they even active on the forum anymore?

Thank you so much, I had missed this one! :thumbup:

I guess it's a combination of safety and technical limitations. Never forget at we're dealing with 50 year old electronics here. Things don't happen quickly as we are used to in the digital era of the 21st century.

Based on what I've read around the internets, as well as statements from real pilots like Mover, I am fairly convinced that our DCS pilot needs a higher G tolerance. I wonder if there are any plans to look into this from ED?

I don't understand the argument for wanting a new engine in DCS 3.0. I think the current engine, graphics-wise, is doing a *very* good job. And it runs very smoothly too (on my pc anyway). What I DO agree with the video in the OP on is that DCS needs to implement some core features to make it more appealing. Specifically: 1. Weather: Weather that looks as good as the rest of the sim. The current clouds and weather model is always the first thing that breaks the photorealism of a screenshot. And not only to be pretty, but to be tactical. Weather is extremely important in air warfare, which also makes it vital that it is synchronized in multiplayer. You can't hide in a cloud if you are the only one who sees the cloud. And for pre-radar era planes (as in ww2), it is just as crucial. 2. Dynamic campaign: This was repeated many times in the video, and I agree. It can really give a lot of immersion and the feeling of being part of something big, without being the center of it. As a part of this comes the demand for better AI, ATC and communication. For the combat aspect, there really is no better way. Scripted campaigns have never appealed to me, and I know that a lot feel the same. 3. Light and dark: External lights, landing lights, city lights, strobes, anti-coll lights... Nothing is balanced. The MiG-21 shines like the sun even in daylight, while the F-14 has external lights that can only be seen from a very short distance. I never fly at night, and I think most of us don't. City lights in Vegas don't look like Vegas, it's just a faded grey area. 4. Terrain: The current map areas are well made, but we need more areas. And especially, we need areas that are not desert. I mean, sure, the Syria map looks nice, but we need more variety. I've personally suggested North Scandinavia/Kola peninsula area... and not only because I live here, but because it's the border between 4 nations (Russia, Finland, Sweden and Norway) and an important blue water area (Barents sea). It's a classical flashpoint for cold war gone hot scenarios as well as more modern takes. You got fjords and valleys, deep frost and darkness in winter, permanent daylight in summer, rough weather, rough seas. The russian Northern Fleet and the northern flank of NATO... (sorry, I got carried away on this point) I think the video by X-check makes some good points, but is way too dramatic. It portrays DCS in such a melancholic and tragic way, that I cannot fully agree with it. DCS is the best flight simulator I've ever flown. It is the best multiplayer experience I've ever had too. It just needs that little extra improvement. Sorry for the long post, but I hope I made some sense.

It works just as I am used to. I never use it without altitude hold though, so maybe that's a thing.

It can also be triggered by things like wake turbulence: (from multiplayer session, so I removed sound)

Was about to post a question about this. My only problem is that I have never flown an F-18, so I don't know what is realistic. But it feels weird that it should get sucked into the ground when all other planes in the sim (that I've tried) do the opposite. You can also feel it when passing low over a ridge or the carrier that the plane jolts down. If it is a bug, I hope it gets fixed, as I've lost more than one Hornet to this.

In my experience, the Viggen works fine for a flying replay (as in, takeoff from runway and fly around a bit). Haven't done any replays of taxiing, but if that is broken, then that is also something that should be fixed. The F-14, however, does not work in replays when flying. It just doesn't pull up when I do in reality and simply flies into the ground immediately (or makes a way too late takeoff before crashing). So, the bugs are different from eachother, but both are Heatblur modules, so there must be some common denominator that is causing it. I just hope Heatblur and ED can figure it out, as I love watching tracks of my "awesome" flying :) It's also very helpful for practicing landing patterns, dogfighting, or just about anything, as you can analyze what you did right and what you did wrong. Sure, you have Tacview, but being able to get into the cockpit and look around while watching my own gameplay is very helpful to learn from my own mistakes. I hope you will make this bug a priority to fix (after the autothrottle CTD bug).

Exactly. As there is still no word from Heatblur on this, we must keep the thread alive.

Pretty sure Razbam will be making the F-15E, considering they've made a deal with Boeing and all that.

Yeah, well, I've posted about it, as have others, multiple times. I can only hope they add a fingerlift or similar keybind some day. I find it very hard to find the exact point of afterburner. Especially when landing on the carrier and wanting to get maximum military thrust, but without engaging the afterburner, in case of bolter. And, as we should all know, you don't want those F110s at full afterburner at low speeds. If one cuts out, you become a frisbee.

Not yet, you can only edit existing steerpoints placed in the mission editor.

Maybe it's where you hang the picture of your wife and kids? ;)

Radar bombing used to be a huge thing back in Vietnam and such. And that works in any weather (with possible extreme exceptions) and light conditions. Not sure if it's still a thing though, as JDAMS are so much easier to deal with against known stationary targets. But currently, I would just say: get below the clouds. Clouds at 1000 feet? stay at 900. Clouds at 100 feet... stay at 90. And use retarded bombs, lest you frag yourself.

I don't know if you can use countermeasures for this. You can trigger an event by having a signal flare in a zone, but I can't see anything for countermeasures. If you want to simulate a show of force, however, you can simply set up a trigger zone and combine it with an altitude condition, so if the player plane is within the trigger zone AND is lower than 1000 feet AGL (or something) then stuff happens. Not sure if it helps.

F-18's ATC and Viggen's AFK auto-throttles are both working. But as someone else said, the auto-throttle in the F-14 tries to maintain on-speed, so I suppose it works a bit differently, and that is where the bug comes from.

Well, considering this thread has so far received no attention from any Heatblur nor any ED people (that we've seen), we don't know if they are aware of this bug or not. If they'd acknowledge that they at least know about it, maybe listed it as a "known bug", then this thread wouldn't have to be bumped all the time. And I will shamelessly keep bumping it until it is seen, not because I am angry or "non-chill", but simply because I want to get it fixed so we can go back to using auto-throttle. But, I think most of us are fairly "chill". It's simply a bug report about a pretty serious bug that causes the game to crash completely. I mean, the sub-forum is called "Bugs and problems" after all. Early access is buggy, and we are all aware, but part of that process is giving feedback to the developers about discovered bugs. So, your comment that we should "chill" out doesn't really make much sense. Do you mean we should stop reporting discovered bugs? How will that help the devs? Or the module?

And yes, can verify that the bug persists after today's open beta patch. Immediate CTD upon activating the auto-throttle.

Whether or not it's a DCS bug or a Tomcat bug doesn't really matter to me. The reason this bug report belongs here in the Heatblur sub-section is because it is Heatblur's module that is active when the problem occurs. No other plane makes the sim crash instantly when you activate auto-throttle. Heatblur and ED have to figure out what is causing it and fix it. I assume they have eachother's contact information.