Jump to content

Docsnuggles

Members
  • Posts

    154
  • Joined

  • Last visited

Everything posted by Docsnuggles

  1. 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.
  2. Docsnuggles

    Napalm

    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
  3. Docsnuggles

    Napalm

    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.
  4. 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...
  5. Docsnuggles

    Napalm

    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.
  6. 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.
  7. 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 ^^
  8. this bug has only become noticed shortly. 2 weeks or so. *cough* Have you already purchased all new stuff? *distract from problems*
  9. Doc is no longer available, can you please reload?
  10. Docsnuggles

    Napalm

    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.
  11. 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.
  12. 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.
  13. 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.
  14. HI, did ED change something in the export name of the FA18? everything works, only the FA18 does not send to the monitors anymore. A10A/C/C2, F16, M2K, Harrier, Ka50, SA342,... all work, only the Hornet does not show on the external monitor. = function(p) return p; end; name = _('CUBESIM 8'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 3840; height = 1080; viewDx = 0; viewDy = 0; aspect = 3840 / 1080; } } -- General LEFT_MFCD = { x = 3920; y = 0; width = 600; height = 600; } RIGHT_MFCD = { x = 4720; y = 0; width = 600; height = 600; } 0 = { x = 3920; y = 0; width = 600; height = 600; } 1 = { x = 4720; y = 0; width = 600; height = 600; } --JF17 JF17_LEFT_MFCD = { x = 3970; y = 80; width = 520; height = 750; } JF17_RIGHT_MFCD = { x = 4770; y = 80; width = 520; height = 750; } -- F14 F14_HSD = { x = 3920; y = 0; width = 600; height = 600; } F14_VDI = { x = 4720; y = 0; width = 600; height = 600; } RIGHTJ_MFCD = { x = 4740; y = 30; width = 560; height = 830; } LEFTJ_MFCD = { x = 3940; y = 30; width = 560; height = 830; } -- M2000 M2000C_VTB = { x = 4720; y = 0; width = 600; height = 600; } M2000_RWR = { x = 3920; y = 0; width = 600; height = 600; } RWR = { x = 3920; y = 0; width = 600; height = 600; } -- Viggen VIGGEN_RADAR = { x = 4720; y = 0; width = 600; height = 600; } VIGGEN_NAV = { x = 3840; y = 60; width = 44; height = 44; } --Gazelle --SA342_TV SA342_TV = { x = 4740; y = 100; width = 590; height = 495; } -- SA342_RWR SA342_RWR = { x = 4140; y = 50; width = 300; height = 300; } --SA342_NADIR NADIR = { x = 3840; y = 0; width = 300; height = 300; } --SA342_WP1 SA342_WP1 = { x = 4730; y = 10; width = 300; height = 90; } --SA342_UHF SA342_UHF = { x = 4040; y = 500; width = 300; height = 100; } --SA342_FM SA342_FM = { x = 4140; y = 400; width = 300; height = 100; } --Ka-50 PVI = { x = 3960; y = 5; width = 200; height = 95; } Ekran = { x = 4180; y = 5; width = 100; height = 95; } UV26 = { x = 4290; y = 5; width = 150; height = 95; } Shkval = { x = 3940; y = 100; width = 590; height = 495; } ABRIS = { x = 4780; y = 25; width = 500; height = 570; } -- Mi-8 UV_26 = { x = 4180; y = 5; width = 100; height = 95; } -- --g_panel_page = --{ -- x = 4780; -- y = 250; -- width = 590; -- height = 495; --} UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center Im actually experimenting but it seems ED changed the names, I did not find a hint, so does anyone know?
  15. check if you have an external program that uses the f7 key, i have this normally with TrackIR
  16. As ED does not manage to build any stable bugfree version even under windows, i guess we would all be happy to have a little fewer bugs, even if it means to built up a linux system. If you ask now "what bugs" well... look in the bug sections, i myself had 10+ tickets over the years due to bugs.
  17. ED has some driver issues imo - as the drivers normally work everywhere else, only DCS is making trouble from time to time; this they could get around as on Linux imo. What about VR (I have a HP G2) ?
  18. technically its easy, and no one needs burning people, but the fire effect should be visible. Else you could also state that the whole cloud thing is just eating memory and too complicated (i guess it was more complicated to build those nice clouds...)
  19. and it would also help ED in building a more stable platform, as you dont have those f*cking MS updateshit that also breaks stuff all the time. As ED is lacking good coders as it seems, this would definitely help and save money for ED in the long run. (edit: and our nerves)
  20. Still a mess. But now also the input on my throttle are bugged, Virpil mongooseT, nothing changed but ED update, in Il2 everything is still fine. Quality... Try use the NVG in the Ka-50. I dont think there are testers actually.
  21. My throttle buttons do sometimes work sometimes not actually, sometimes after restart. Virpil MongoosT (first one). 4 weeks pause from DCS, before everything fgine, now a mess. I did not install any updates of Virpil, but ED ran some. Btw, in Il2 everything is normal and running fine.
  22. update again: on takeoff i had now a ctd. No other game makes such troubles as DCS actually. Clean install, no mods.
  23. I had the same issue - its definitely not Virpil, ED messed around with input in the updates it seems. Restarting DCS now in the first time fixed it for me atm.
×
×
  • Create New...