Darkdiz

OK, thanks. I'll copy the above into my notes binder, and re-edit

Think I got it fixed. Apparently the views.lua in the main game mods/aircraft/aircraft name folder is the answer. I edited the main game file (not sure if it will pass IC) but also copied it into a newly created folder in my saved games/mods/aircraft/aircraft name folder. Changed line 4 to change 140 to 210. I disabled the saved games server.lua (renamed it server.old), and it still worked, so I'm not sure this file has an effect. Obviously a few more tests to be run!

I still have the server.lua (unedited) in my main game folder. I also found another views.lua file in the mods folder in the main game folder under mods/aircraft, I included the FW190 version as well (there is also a Spitty version). This one may be the issue, as it is very similar to the snapview.lua SnapViews.lua Views.lua Server.lua

Sigh, still not working for me, clearly more research to be done. I changed my Ch13 FOV on both my Spit MkIX and Anton to 105 (decided that 115 was a little TOO wide), but the view still was far too narrow on spawn (it is somewhere around 60), until I hit NUMPAD Enter, when it then reverted to whatever zoom I put into Ch13. Even playing around with the server.lua (copied and pasted into my user files folder) didn't seem to work under the cameraviewanglelimits line. The slider remains unallocated, using a seperate binding for zoom in/out slow until I can sort it out

I'll have another look at this, and play around with it, as it seems to be the preferred solution

Well, not the best option, but I fixed it by deleting the zoom function on the slider axis, and instead put the zoom function as Zoom in/out slow onto another key.

Hmmm, no luck. It appears that the server.lua is no longer edited based on the rem statements in it (see below, this is line 16). 16 --this file is no longer should be edited for adding new flyable aircraft , DCS automatically check core database (i.e. where you define your aircraft in aircraft table just define ViewSettings and SnapViews tables) I looked for a viewsettings.lua (found the snapviews.lua but this doesn't seem to include the default spawn view). Scratching my head here...

I just purchased the FW190A8 and Spit Mk IX, and am finding that when I spawn, my default spawn zoom position is too narrow. I edited the SnapViews.lua to make the default zoom 115, which it seems to start at, with the initial fly screen visible. But when I hit fly, it reverts to about 80. If I hit the numpad enter key (zoom normal) it goes back to where I want it. How do I set it up so the spawn zoom is 115 so I don't have to hit the enter key? I don't seem to have that problem with my other planes

Outstanding! Thanks for the quick reply. One other question... The pilot body defaults to on, even though I have it turned off in settings, and I have to press RShift+p to turn it off. Is there a way to have it default to off? This only appears to happen in the RIO seat, the pilot seat appears to obey the settings command

First off, LOVE the F-14 module, best DCS investment I have made to date. I especially enjoy the RIO aspect. My question arises from the HOJ capability for the AIM7 and 54 with the latest update. HOW does the RIO command this? Is it automatic? Are there any switches that need to be made to optimize/invoke this mode? Thanks

Hey does anyone know the names I need to put into the monitor setup lua file for the F-14 Airspeed Indicator and master caution panel? I have a heck of a time seeing them, so thought it would be a possible solution to put them on my MFDs

Downloaded the file, but I keep getting unrecoverable errors Extracting to "D:\Updates\DCS\Mods\Military_Aircraft_Mod_V1.7.1a\" Use Path: yes Overlay Files: no Extracting Military Aircraft Mod\A400M_Atlas.lua Irrecoverable Error: Attempt to access a file detail that isn't specified. This happens even if I individually select each file Can anyone help?

There is NOTHING that beats cruising along at night with Dark Side of the Moon playing in your headset. I have actually done that in real life, back in the day...

@near_blind You sir, are a rock star!

Still trying to get the B-side tracks to work, currently when I flip the cassette, I get silence. I have the ogg files as Song1.ogg, Song2.ogg etc in the Walkman folder, seems to work. Is there a proper syntax for songs on the b-side? Is there a resource somewhere that explains the parameters for the files and controls, ie how to FF to song 2 (or can it even do that?)

Hi: Just discovered this really nice enhancement to the already nicely done F-14. My question is that if I want everyone on my server to have the same playlist of F-14 walkman ogg files, is there any way to include the files in the miz file, and if so, where do they go? Pretty sure I would have to manually include them (drag and drop into the miz file once it has been created), but which folder would I have to place them in? Would it be direct into the miz file? Or would I have to put the ogg files into perhaps somewhere in the l10n folder?

So, after more testing, and a bit of research, this is what I came up with... (From the Heatblur Manual) The LANTIRN steering cues for ground target engagement are automatically enabled when the LANTIRN is slewed to QDES or a new QDES is designated. The QDES itself will remain even if a new Q is selected and as long as it exists, the steering cues will point towards QDES even if slewed to another point. This is important to keep in mind as it is easy to think that the steering commands is to the current sensor location instead of the QDES. Although I'm pretty sure I QDES'd the second tgt... Worked as advertised this evening though, 4 direct hits on 4 separate runs. Interesting in that I lased the second tgt, one would think the weapon would track to the laser, and not the original QDES point?

I’ll have a look later today

This is similar, but on seperate runs more than a few minutes apart. We went out to about 10 miles after the first launch (I was the RIO, this is NOT a Jester controlled launch). Never lost the target area (always had QDES locked), dropped on the second run on a second target about 50 yds away, laser was locked onto this tgt in Point track, second LGB guided to the first impact point. I think in your case, the LGB may not have time to see the laser, as it has to arm itself once released, hence the miss. LGBs need at least 5-6 secs of laser prior to release to guide properly in my experience

Now before anyone goes on a rant saying I'm not doing it right, hear me out... This is REPEATABLE, and has happened every time I have launched more than one LGB since the last update. Observation: First LGB hits designated target as expected, no issues. However the second LGB, even though a different target in the same general area (50-100yds away) is newly designated (QDES then Area Track to second tgt, then Point or Area Track as the case may be) impacts exactly where the first target was designated, as if I was designating the first target, not the second. Its like the second bomb locks onto the first target. Tested on at least 6 occasions, each time the same result, regardless of area/point track, WHOT/BHOT, even if I undesignate, then egress out to 15 miles or so and re-run in etc. Second designated tgt clearly in the cross-hairs, weapon clearly misses and hits original designated spot (center of now burned-out tank, the first tgt). Laser on second target and not moved from 10 secs prior to release to impact (which is clearly visible on first target). All tests done in a sanitized area with no enemy present, codes all at 1688, drop height ~12000', wings level, TTI apx 35secs from release, wpn GBU-12, but also noticed the same on GBU-10 and 16 (24 not tested). Anyone else have this issue? Or Am I missing something?

I found that you have to tweak the lua file until you hit the sweet spot. I'll attach my file, feel free to edit as necessary. I have my main screen as 1920x1080, with 2 x 800x600 below lined up with the left and right corners. The F-14 screens had to be significantly tweaked, mostly by trial and error. 1_Screen+2xMFCDs_below.lua

No, just McAfee. All necessary ports (8088) open and forwarded. Weird that I can control it from my phone or on the host machine no issues, just no response when I try it through the ED site with my laptop. Its OBVIOUSLY something stupid, but it is evading me...

Hi: I have the DCS Open Beta Server installed on my main desktop, but would like to control it through the webgui from another computer on my LAN. It USED to work fine, I run LOTATC etc from the laptop, connects no issues, but for some reason when I run the webgui from the laptop, it won't connect at all to the running server on my desktop. I can connect through my phone no problems, or on the host desktop, but all I get is server not responding from the laptop. Clearly I'm missing something here. Anyone have any ideas?

I know on the pilot side the ARC-159 Main/Both switch is screwed up as well. Any idea on which lua the Cmd button is in?

I have this button mapped to my keyboard, and when activated, it sticks in the down position. I tried re-mapping it to one of my MFD buttons, same issue. To clear it, you have to mouse click it. Easy fix? Clearly when remapped to a seperate button the press function works, but the release function is missing, causing the button to remain in the pressed position.