Jump to content

Darkdiz

Members
  • Posts

    230
  • Joined

  • Last visited

Everything posted by Darkdiz

  1. Got it figured out...
  2. Hi: First off, absolutely LOVE this plane. Trying to dial her in, I used to use a snapview to lean into the gunsight (I use Track IR, so the snapview would stick until I released the key). Then I discovered the Cockpit Panel View Toggle, which ALMOST puts me in the proper position behind the gunsight, but needs to be tweaked quite a bit, as it is centered in the cockpit looking forward, but the gunsight is off to the right. The plus of this method is I press the key once to toggle this view which sticks, and then press again to go back to track IR. I just need to move the camera position of this view a bit to the right. I'm pretty sure it is going to be in a lua file somewhere, but I can't find it. When I'm in panel view, the camera view move keys (RCTL + RSHIFT + NUMPAD whatever) don't do anything, so not sure HOW to move this position. I put the camera coords for this onto the clipboard, they are: -camera -34.100774 0.059272 -10.257918 -cameradir -0.925764 0.206867 -0.316493 Any help would be fabulous!
  3. Nope, I did NOT have a good experience with it or JSGME. Prefer manual
  4. Well done. I adjusted the Adobe export setting to make the png colourspace RGB instead of auto. Worked fine. Thanks for the quick response
  5. Ok, so I guess its in the Adobe export? Just make it more colour depth?
  6. The method I use is to save the selected pages from MS Word as a pdf, then export the pdf from Adobe to png. This has always worked fine prior to today, I have created a multitude of pages for my kneeboard folder, all displayed correctly with default settings. GIMP was not involved at any time in the process. I thought it might have been a DCS setting or something in a lua file somewhere, but I noticed that one of the pages I exported rendered correctly, it had multi colours in it. I ended up making the para numbers red, and it solved the issue (or at least band-aided it)
  7. I got it to show up correctly. If the png has only 2 colours (black text, white background), in DCS the background shows up red (at least for me). I fixed it by by making some of the characters in the working png red, and now it appears normally. Weird in that in all of the other graphics programs the png appears normal. I'll take a screenie of both... I also attached both files. 01a shows up red on the kneeboard
  8. I recently created several png files for the kneeboard. Previously, these have shown up correctly, white background. However, the last set I created show up on the kneeboard with a red background, even though in any graphics program (GIMP, and of the Windows graphics apps) they show up as expected with a white background. The pngs were created by exporting a MS Word page to pdf, then exporting the pdf page as an image png. This has worked fine before, and the old ones I still have in the kneeboard folder show up correctly. The one page that DOES show correctly has an image embedded in the original file. Any ideas?
  9. Main Game/Mods/Aircraft/F14/Cockpit/Scripts/ControlsIndicator/ControlsIndicator_page.lua The background transparency line is 45, make them all 0 in the { } brackets, the position line is 67, I edited mine as above from {0,-(1 - 1.5*totalSizeX)}, there are several lines for colour, I just edited wherever it said texture_lightgreen (except line 3 which I left alone) and replaced with texture_red (there are 8 instances in the file)
  10. So what I do... take the edited file, make a copy of it, rename it something else (materials.new or something like that). When there is an update, this will stay in the folder unchanged. Then, after the update, take the updated materials.lua file (which the update would have... updated back to the original without your edits) and rename it materials.old. Copy the materials.new, paste it, then rename it materials.lua. Voila, back to what you want it to be. Once you have done it once, it becomes easy, it is what I do for LoTATC and some server scripts I run
  11. ...aaaaand figured out the colour Turns out you have to edit the same lua file by changing all instances of texture_lightgreen to texture_red. You can then edit the local texture_red = MakeMaterial ("arcade.tga",{255, 0, 176, 255}) as required to get whatever colour you want. Now to figure out how to have that stick and not have to do it after each update
  12. There HAS to be a lua file somewhere that you could edit to make this brighter. The question is where and which one?
  13. Dumb question, but is the actual brightness on the monitor up?
  14. Hmmm, Ok, but I don't find it an issue, I guess I just got lucky and found a good balance
  15. I have it figured out, ended up being (0.05, -0.65) Perfectly aligned in the lower left Cougar Now to figure out the colour!
  16. Hey are you guys still looking for F14 folks? Fairly experienced RIO here, I could come complete with my own pilot as well.
  17. I’ll have to fool around with the x,y numbers to get it cantered where I want it. If I do the math it’s (0, -0.7) currently. How did you get it to show up in red?
  18. You can also increase the actual TID brightness
  19. Hi In the ControlsIndicator_page.lua, {0,-(1 - 1.5*totalSizeX)} is what shows in the base.init_pos (line 67). How do I adjust that, as I'm not sure which variable controls which element of the indicator's position. Right now, it shows up on the bottom of my Left Cougar display, but is annoyingly off-center, so it doesn't have to move much
  20. Happens the same for me, the HSD version exported is a bit dimmer. I just increase the HSD brightness
  21. Apparently its a known bug, when you put an axis onto the Tgt Des hat on the Warthog Throttle (Thr Y-axis) the Y-axis on the joystick comes up with the red exclamation point. I deleted that axis-binding, and so the exclamation point disappeared, everything returned to as it is supposed to be. Clearly a bug, not sure if is officially reported though. It works until you exit and then come back into DCS, when you get the red exclamation point. Issue has been around since at least 2019, based on the pic a buddy sent me. Based on the amount of time it has been around it seems unlikely to be addressed any time soon, if at all
  22. Warthog joystick, was working fine. I got into my jet, tried to take-off, no pitch input at all. Checked the bindings, sure enough the red exclamation point is there. Only for the F14, works fine for all my other planes. Tried binding a different joystick, same thing, no pitch. Tried re-binding, still no pitch. Roll input is fine though, pitch input is seen in all other planes. Anyone seen this before?
  23. Hmmm, not sure. I ended up just making the ships actual ships instead of statics, joined them into the CV group. At least they spawned in place
  24. Hi: I recently created a miz and have set up static CVN support ships at specific distances from the CVN. In the mission editor, I linked these static ships to the central CVN, and they appear to be in the correct place in ME. However, when I run the miz, they spawn at the correct distance from the bullseye, as if the BE was the CVN. Miz attached. Any thoughts? Syria 102 Template.miz
  25. Seems to work, thanks @Rudel_chwfor the help! Funny how the lua worked fine once I got the syntax sorted out (had the FW correct, but forgot to put the Spit name in between "", one worked, one didn't. Go figure!) Still have to fine-tune initial head position, I feel I'm a tad too far back, but that is for another day!
×
×
  • Create New...