-
Posts
154 -
Joined
-
Last visited
Personal Information
-
Flight Simulators
DCS nearly all modules, IL-2, Elite Dangerous
-
Location
Germany
-
Interests
Combat Flight Sims, RPG, ED
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
I brought up the idea of a "subscription base" for people who want it, and then in exchange pay less for new models, get early access and so on; so ED would have enough funds to fix old bugs and problems, the way they act today is more like a snowball company that will someday collapse.
-
Oh pardon to wake up someone on ED and remind that there are very old promised features still not taken care of, that were listed as features and are still listed. Perhaps ED should finish sold stuff before selling new unfinished stuff, would be nice for customers, but thats just my opinion. If you dont like it - well, I dont care
-
i know the difference between a fire and a cluster explosion, it was just for comparing that it IS possible as both use similar calculation power on PCs - whereas a BK90 has perhaps more to calculate depending on how they model it.
-
thats nothing in ED terms. look at the bugs in other modules, for example the NVG reflections in the Ka50 or the crappy reflections in some planes.... 1-2 years or longer reported...
-
thats the ED 2 weeks. normal timeframe, just look on when some bugs are reported and when they get fixed look at the BK90 effects, its possible.... they are just unwilling which i do not understand.
-
try the training mission for the grom and then setup a simple kill ship and try the same. here it is totally different. in the ED training mission the pipper stays on target, in the self made mission not. Either the training mission is wrong or what is told here is wrong. anyway, the training mission should reflect what needs to be done.
-
Docsnuggles started following Kegetys
-
when I said that over a year ago first time that in some models there is an issue I was harrassed by fanboys... now we have those f*** issues in nearly every module; it was first in the su-25 / T and the A-10A; then in all other planes ED "Updated" with this buggy things. I even sent TRK / Screens to the support, but it is ignored. Better, Bigtralalaa muted me a time for being too "explicit" after months of talking and nothing happend. Those reflections are even worse when you fly nightmissions with NVGs in the Ka-50. You aint see a s**t. let them fix the actual mess first, god knows what they break when they implement that... I own nearly every module aside some warbirds; for warbirds i use IL2 - much better damage models, smoother and imo also a great modelwork, except you are an ED fanboy ^^
-
Docsnuggles started following Taz1004
-
this bug has only become noticed shortly. 2 weeks or so. *cough* Have you already purchased all new stuff? *distract from problems*
-
Better Smoke V22 for DCS 2.9
Docsnuggles replied to Taz1004's topic in Utility/Program Mods for DCS World
very cool, thx ! -
Doc is no longer available, can you please reload?
-
any news on ths? I mean noone needs splatter effects like in Doom, but a fire exposion & burn effect should be included; the effects of the BK-90 prove its possible.
-
Do not buy anything from Cubesim
Docsnuggles replied to Canlenkrow's topic in PC Hardware and Related Software
hm, i ordered mine befor this covid mess and got them and still they work fine. I now ordered 2 new and I knew it will take long, due to the problems everywhere actually so I wait. But its good to see there is an alternative. -
2 weeks....
-
How is the new Pandemic Campaign?
Docsnuggles replied to LotusDragon's topic in DCS: Ka-50 Black Shark
thats what I meant with technical cra** ermm, issues. in waypoints, the triggers are - different. But as some people like to fly the same mission 20 times to detect the trigger maybe its just me wondering if this is correct. As I said, the other campaigns are a bit harder imo, thats not what I say - its easy but boring to encounter technical bugs, designbugs. -
Found a solution, simply renamed the ports, now it works again: F18_LEFT = { x = 3920; y = 0; width = 600; height = 600; } F18_RIGHT = { x = 4720; y = 0; width = 600; height = 600; } Additional in the MDI_left_viewport_cfg.lua: --ViewportHandling dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") update_screenspace_diplacement(1, true, 0) try_find_assigned_viewport("F18_LEFT") and in right also.