

dorianR666
Members-
Posts
1625 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by dorianR666
-
fixed Extraordinarily bizarre damage behaviour of F-shape barrier
dorianR666 replied to dorianR666's topic in Weapon Bugs
in fact, it gets even worse. @Flappie some objects lose their collision boxes and can be repeatedly shot through (T90, soldiers, BMP3). and the guard tower becomes green when hit. the T90 later regains collision box for 30mm cannon. i suspect this whole bug cuts far deeper than it seems at first sight. memory writes into wrong locations, scrambling both physics and graphics? or some incompatibility between weapons and static objects? 2.trk this whole mission, or maybe this particular CA vehicle, or its weapons, behave insane. -
fixed Extraordinarily bizarre damage behaviour of F-shape barrier
dorianR666 replied to dorianR666's topic in Weapon Bugs
it isnt fixed f_shape.trk -
Flickering and glitches happening under certain conditions.
dorianR666 replied to Rainbowgeorge's topic in 2D Video Bugs
like this? please make a post there. -
Unreliable track files, please make them use able again.
dorianR666 replied to Maverick_NL's topic in General Bugs
Ive had a track fail within 2 minutes. It didnt record my keyboard press-and-hold of rudder input on taxiway, resulting in me going full afterburner 90 degrees perpendicular to runway during replays. It seemingly forgot to insert that input into the trackfile. There are software bugs in the trackfile functionality that simply are less probable to manifest in short trackfiles. But they fail too sometimes, rarely, but they do.- 53 replies
-
- unreliable track
- recording
-
(and 3 more)
Tagged with:
-
is something like this intentional ED? seems a bit excessive to me. they also tend to fly perfectly horizontally while all other smokes go more up (can be seen in these screenshots).
-
i have seen this too. sometimes vehicle smoke is extremely wide or long, it looks like an oil refinery is on fire instead of a truck. no idea how to replicate it.
-
Did you try running DCS repair?
-
[NOTBUG] Time to waypoint not working?
dorianR666 replied to Tinchus2009's topic in Bugs and Problems
Ah, I get it now. I got confused by your screenshot pointing at the mission editor ETA field. Thats there mostly to setup TOT with the checkbox on the right. What you describe is weird indeed and sounds like a bug. -
[NOTBUG] Time to waypoint not working?
dorianR666 replied to Tinchus2009's topic in Bugs and Problems
that looks like chucks guide to me. its unofficial community-made guide, not module manual. its contents are derived from observed gameplay, not prescriptive of how the game/aircraft should behave. TOT cannot be automatically calculated for F10 marks because there isnt a way to specify airspeed or time for them, unlike mission editor waypoints. you must enter TOT manually for these waypoints in cockpit. -
DCS: F/A-18C Features Roadmap for Early Access
dorianR666 replied to Kate Perederko's topic in DCS: F/A-18C
Dont forget EMCON and its HOTAS logic. Edit: WobblyFlops already mentioned this. IIRC, ED said that they wont do this one. -
cant wait for this. is there a good chance for release this summer?
-
Unable to fire HARM in SP Pullback when in A/A mode
dorianR666 replied to ZBoT's topic in DCS: F/A-18C
yes, this stopped working. -
hi not much to explain here: the afterburner effect is also wider than the nozzle: m2000_ab_bug.trk gamma 2.3
-
already reported Ship wake still broken.
dorianR666 replied to Skysurfer's topic in Bugs and Problems
its kind of a big deal actually. it makes some campaign missions unplayable. -
hi, thanks for info. this will be useful for me in future mission making. the indices are fine, i tested it in editor. must have been a user error on my part, with making markpoints unprecisely at 9k.
-
hm, i checked the mission triggers and it checks for two cockpit button presses for the markpoint creation, while being in a zone. i made the markpoint at higher altitude to avoid ground fire, and so i may have been unprecise. i guess that explains it. still weird about the screenshot though.
-
the thing happens with like 30 minute delay. i got this after i flew all the way (100+ nm) home and landed. bug?
-
could it be because my wingman keeps crashing into terrain every time? is he supposed to say something? i now found out i can still RTB and get 52 result, but there is absolutely nothing telling me to RTB and no message after landing (that may be intended). its like the mission abruptly ends after killing the manpads, nothing is heard or shown afterwards.
-
I dont get it. I report detail on the crash site. Vehicle moves into the compound. Im told to create markpoint on the crashsite. While doing that, I get shot at by the manpads and get told to destroy it. I destroy the manpads. Cool, I can now do the markpoint. I do the markpoint. Nothing happens after that. Im not getting any radio messages. Im circling above and nothing happens. According to youtube videos, there are supposed to be reinforcements coming and im expected to choose between attack or RTB. This never happens to me. Very frustrating. What am I doing wrong? Whats the trigger im missing? BD, for future campaigns, consider adding an F10 command "Current task?" that will give me a simple text message describing what I'm supposed to do at given moment, for people like me :). With these trigger complicated missions it gets confusing. Or maybe Im just dumb.
-
fixed, thanks
-
same, this is reported i think. TOO is all around broken right now.
-
yes, i was answering the question in the post. not the question in thread title.
-
as far as i know - no. you have to support the missile until pitbull or it will fly straight (instead of extrapolation of targets movement).