Jump to content

tacca

Members
  • Posts

    160
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by tacca

  1. its a hold over from an old version of the mod (DCS2.2) where there was two different NVG effects depending whether you were in a NATO or Soviet aircraft. I've yet to look into whether DCS still implements this using the NVD_HDR.fx file or elsewhere
  2. Really simple fix to make the current version have more noise, Reduce the lift value and/or increase the nvg_noise value. What discord group is that from, I can't access the post. And not sure if you are refering to me about getting a VR headset but if so I havent been able to afford the GPU/VR headset cost the last 3 years so unlikely to be any time soon.
  3. Hey PJ, i completely understand the problem but this has to do with 3d reprojections and without a VR headset I have no way to trial possible solutions. To be clear I have zero background in shaders or coding, just handy at maths and some patience combined with LOTS of trial and error. I have an inkling about where I might need to start but no way to try.
  4. Hey All Version 1.4 is now up NOTE - SIGNIFICANT CHANGES TO HOW VALUES ARE INTERPRETED. Suggest starting fresh with the MOD_nvg file in the download and update/play with values slowly This is also missing thr depth of field blur effect. That is next on lost of features. Version 1.4 - 22 March 2023 Features: NEW - Change colour, noise levels or contrast NEW - Ring/tubes/google number option - simulate monocular/biocular/quadocular NVGs - THANKS TO RYUK47 for this code addition Set NVG center point, size and ring dimensions Black ring effect with adjustable thickness settings. Variable render mode options Fixed folder naming issue to be truly OVGME ready Download here. OVGME read. As per old mod, change settings BEFORE APPLYING MOD
  5. So good news all. I made a fair bit of progress over the last 2 days and I have sorted out the following controls/options - contrast - NVG color (eg what shade of green) - noise pattern (sprite type, size, timing) - noise intensity (much reduced by my current default as I think DCS is way over done) Doing all this though means using my own RBG-HSL/tinge-RGB conversion which means the default depth of field blur doesnt work. That is my next priorty over the next week and once I have that done Ill upload it all as a new version rather than drip feeding mod versions. Screen shots show 1. high contrast -this wouldnt be default but just evidence that everyone will be able to tweak the pickup/intensity curves 2. mid contrast - what ill probably have as stock settings 3. ring effect and my stock color 4 & 5. alternative color choice (also shows how moonlight/trees casting shadows is visible using my NVG amplification curves)
  6. Link is fixed on first page, thanks for that.
  7. Version 1.3.1 - 15 March 2023 - IM BACK!! Can be downloaded here or on first post Change log Fixed for to work with DCS 2.8 and Multi threading versions. Removed noise files as DCS incoportates simplex and perlin noise calculation .lua's Future focus - noise and color user control - additional viewport options
  8. Hey HeloGuy. I am back working on this and trying to implement all the old features that I had working back at the start of DCS2.2 As part of that you will be able to change color but im not quite there yet. @Ryuk47 has also done some work to the mod with regards to different viewports. We are going to combine our work and update here once we have done that (im also moving it all to gihub to make maintainance much easier etc). @VR Flight Guy in PJ Pants As I have said previously I dont have a VR headset so I am unfortunately blind how this mod performs in VR. Until I get a new GPU (still rocking GTX1070) and a vr headset I am going to have to rely on others. @MTrenda Thanks for that. makes sense
  9. Hey Mtrenda, I have just come back to DCS after not using it for over 2 years. I was just wondering how you found this error as the format of DCS logs seems to have changed. It used to be pretty explicit listing file/line of code/variable that was the issue but now it is a jumble of hex code?
  10. Re did the whole first post to remove all the extraneous crap.
  11. Hey all, updated link so people shouldn't have to request access because of the google drive hotkey change https://drive.google.com/file/d/0B1s7D5Bzv2DFUkNtcWNZbWZTaXc/view?usp=sharing&resourcekey=0-84_ByCVzfjV0I7jryVoHig
  12. From the first post: Eye Size and position: EYE_CENTER = sets center point of NVG effect on screen as percentage of X and Y starting at bottom left corner. eg (0.5f, 0.655f) = 50% across and 65.5% up. [b][u]EYE_SIZE = Sets X and Y diameter of NVG as percentage of screen size. eg (0.47f, 0.75f) = 47% of width of screen and 75% of screen height. Since most monitors aren’t square the y value will have to be larger than the x value to make a perfect circle; the ratio between the two numbers will be the same as your monitor aspect ratio[/u][/b]
  13. Hey, if the whole screen is green it might be the mode option. Make sure the following line (line 13 of MOD_nvg.hlsl) is set to =2 static const int RenderMode = 2;
  14. For anyone wondering about the naming of the string value and how to get it here are the full steps for setting/changing the default profile of a X52 or x52 Pro when you have the newer Logitech drivers/software installed: 1. open regedit 2. go to HKEY_LOCAL_MACHINE\SOFTWARE\Logitech\Configuration\Controllers and copy the name of the folder there including curly braces, mine was {C7719F41-F667-4514-BBB4-3F38C9E4D05A} yours will be different as it is your device ID 3. Go to HKEY_CURRENT_USER\Software\Logitech\Configuration\StartupProfiles\ if the folder/s dont exist make them by right clicking and choosing make new key. 4. make a new string value in the StartupProfiles folder (you cant edit the default one) where the name of the string is the is ID you got in step 2 (include the curly braces) 5. Right click on this string and choose modify, in the value data box copy in the file path to your profile that you want to load as default. eg mine is C:\Users\Public\Documents\Logitech\X52\HOTAS - DCS - A10C - IR.pr0 you need to include the .pr0 on the end
  15. Hey Rephil, are you using JSGME, OVGME or just straight installing the mod into the DCS install folder? Can you send me your MOD_nvg.hlsl file and I will take a look.
  16. Hey Yeti, do the following With the mod UNAPPLIED if you using JSGME/OVGME Open “MOD FOLDER"\Tacca's NVG mod 1.2.0\Bazar\shaders\common\MOD_nvg.hlsl adjust the below numbers in bold that are a few lines down in the file //overall NVG postion and size static const float2 EYE_CENTER = float2(0.5f, [b]0.655f[/b]); // SETS CENTER POINT OF NVG EFFECT ON SCREEN static const float2 EYE_SIZE = float2(0.47f, [b]0.75f[/b]); // SETS X AND Y DIAMETER OF NVG (PERCENTAGE OF SCREEN) save file REAPPLY MOD The first bold number sets the vertical center point of the nvg ring (.65 is 65% of the way up your screen) the second bold number sets the vertical size of the nvg ring (.75 is 75% of the height of your screen)
  17. Glad to hear people are still enjoying it :)
  18. Hey PeaceSells Could you explain/show code on how exactly you were able to pull out all the function names? are you using debug messages or somehow saving out to a log file. just starting to get my head around all this but the ability to call/save/display all values in a table would be super helpful. Cheers
  19. Thanks Skate, pretty much as I thought. Your help has been much appreciated :) Now just down to playing with numbers to get realistic looking nav and anti-coll lights (intensity of lights and how much they light up surrounds)
  20. Thanks Skate, I had seen your first video but not the second one. Is it best practice now to just use 3ds max lights and not place any point helpers at all? Looking at the Christian eagle edm file and also the aircraft lua they call arguments for the lights and type name but no at all connectors (in lights section of lua or on model). Cheers Tacca
  21. Hey, did you ever find info on this else where? I have added comments to the parts I know but the others are still a mystery k_adiab_1 = 0.037923, k_adiab_2 = 0.0562, MAX_Manifold_P_1 = 180000, -- from study of aircraft files these manifold pressures should be increasing in value and not the same. not sure what they represent though MAX_Manifold_P_2 = 180000, MAX_Manifold_P_3 = 180000, k_after_cool = 0.0, Displ = 35, --displacement in litres k_Eps = 6.5, Stroke = 0.165, --stroke in meters V_pist_0 = 13, -- number of pistons Nu_0 = 1.2, Nu_1 = 0.9, Nu_2 = 0.001, N_indic_0 = 1052480, N_fr_0 = 0.04, N_fr_1 = 0.001, Init_Mom = 220, D_prop = 3.5, --diameter of prop in meters MOI_prop = 45, -- moment of inertia of prop (not sure of units, probably kg * m^2) k_gearbox = 2.088, -- prop to engine ratio (gearbox ratio) eg (P51D - Prop reduction ratio=0.477, 1/0.477 = 2.088) ---------- -- all of below have the exact same figures for both the p51d and l16 so not sure if they do much --------- P_oil = 495438, k_boost = 3, k_cfug = 0.003, k_oil = 0.00004, k_piston = 3000, k_reg = 0.003, k_vel = 0.017,
  22. Hey Skate can you provided a description of how to properly control lights within 3ds Max or a link to something that is up to date? Do you still use dummies/connectors? Cheers
  23. Just a little heads up for anyone trying this. You need to put the mod files in your saved games/dcs/mods/aircraft folder and NOT in the actual game directory, otherwise is wont load.
  24. Hey Ams, thanks for the update. the laserbeam.hlsl was fixing a masking issue when using the IR laser beam. More details can be seen here: https://forums.eagle.ru/showpost.php?p=2546081&postcount=38 but basically while the laser should be visible inside the NVG but not outside of it (it is IR light so not visible to the naked eye). If deleting the laserbeam.hlsl fixes the flashing bug and you cant see the laser outside of the ring then ED have fixed/updated some of their code and its not needed anymore.:thumbup: Cheers
  25. Read the very first post, it explains how to change that :thumbup::music_whistling:
×
×
  • Create New...