Tailhook

This has been implemented for months now, just make sure the box is checked in options...

That would explain some things. Yeah, the wing fold probably shouldn't come down with auto-start.

Works fine for me on 2.5.5.:huh:

For anyone wondering, the new function is LShift + Right Click

2.5.5 Doesn't seem to be possible to middle click and hold to move the aircraft around in Default view anymore. Looks like it's been changed to just having to left click and hold while in top/bottom/side view. Seems inconvenient now cause you can no longer orbit around a specific spot since Default view remains locked to the center of the model.

The jet and cockpit are already UVW unwrapped AND textured. This isn't going to happen.

No thanks. Given into account how bad A LOT of people are at refueling, if I randomly disconnect I don't want to have to look back down at the fuel gauge and then flip through the comm menu to select a new amount or 'TOP OFF' every time. Switch the mechanics the other way around, someone could tell the tanker how much they want and then struggle to connect, then the whole specified amount thing is just pointless because they will then have to specify more fuel because they just burned more while trying to connect.

No. The current update will be a free upgrade, external and cockpit models, but to unlock addition functionality you will have to pay.

Like Hendrix said, you don't need TARGET. I experimented once with having left mouse mapped to forward on the comm hat on the throttle but changed it to COMM2 instead, and it also wasn't great for dials. Sadly I prefer a bunch of functions on my HOTAS so I'm stuck with the mouse. The script timeout that you are getting is typically caused by having the TeamSpeak Hotkey plugin installed and/or TeamSpeak open while executing the script. I would also suggest unplugging and replugging the HOTAS into a USB2 port, wait, then back into the original port to correct the driver issue without having to restart computer.

I can support this. +1

Are you calling it in the LODS file? And did you make collision lines as well?

I was trying for a while but gave up and stopped caring cause Overwolf doesn't seem to care. I don't even think they check the support request list because all the games on there have been listed for years and still no change.

https://forums.eagle.ru/showpost.php?p=3915924&postcount=95 The only way to make this module work and keep everyone happy is the bare 3D model itself needs to be a free addition for the sim that everyone can land on and shoot off from. It doesn't have to be functional, it just has to be available server-wide. Whatever payware features there are should be configurable like suggested in my previous post. Give mission makers/server owners the ability to enable and disable things but also have specific things hard disabled for multiplayer, or something similar to that nature.

Technically impossible, you have to replay the track in 2D. However, you can locally record a cropped 16:9 video of your flight with OBS/Xsplit but it won't be nearly as spectacular as a 4K 2D image.

Looks like driver or overclock related. Either way, try running a repair/cleanup and remove any terrain mods.

The only major (actually minor) cosmetic difference from a 3D model standpoint for a simulator would maybe be the George HW Bush, but who really cares, it's still a Nimitz body. Slap the 77 on her and call it good.:)

With how awkward things can look when people are lagging or in a rush to get in the air, things can be a mess. The deck sliding still needs to be addressed more (or has with this module?) because the way it seems it was "fixed" was by just making the carrier a flat surface allowing the model to slide around under the wheels. As a result, unless the wheels contact the deck directly it won't be possible to simulate a pitching deck in a storm and the sea would have to be multiplayer synced if it isn't already. Please define "other". This is what I don't want to see. I don't agree with keeping both old carriers, if that is what you mean by other carriers, when an even newer model and new standard is available. The Stennis was a pleasant improvement but with the new Nimitz coming, it will then be EOL with the Vinson. I don't know if it's a mission compatibility thing but I'd rather see them be removed so things are kept tidy and organized, missions will get updated. The new model could be both utilized with very basic enhanced features or simply none at all, hence a platform upgrade. Simple automated/controllable Shooter and LSO models/cameras would be enough to make me happy when online, everything else can be kept locked to a bought-only server and singleplayer. Regardless, under Ships in the mission editor I don't want to have to choose between 3 different quality versions but rather have all 10 Nimitz-class CVN's of the same quality for once. Give mission makers/server admins a checklist of functions they can enable and disable and have the high fidelity options auto-detected and grayed out when hosting the mission over multiplayer, or something of that nature. I wish I knew exactly what is being done so I could better judge how it could be multiplayer compatible. It would be great if the new carrier came with just one 3D model and all 10 CVN liveries but the only issue I see with that is the numbers (and number lighting) on the island. If ED could figure out how to make that work instead of having to supply 10 different models, that would be awesome. Aside from that, the liveries could easily be adjusted by argument timing in the livery description LUA just like the aircraft board numbers. Arg timing example: 0.00-0.10 - CVN-68 0.11-0.20 - CVN-69 0.21-0.30 - CVN-70 0.31-0.40 - CVN-71 0.41-0.50 - CVN-72 0.51-0.60 - CVN-73 0.61-0.70 - CVN-74 0.71-0.80 - CVN-75 0.81-0.90 - CVN-76 0.91-1.00 - CVN-77 ATC in general should be an overhauled core function. Both land and sea ATC should feed from the same directory like currently and keep specific high quality module-based ATC calls to payware which would be downloaded along with the carrier module itself. WW2 is only "dead" currently because there aren't more aircraft to select from YET. A sweet online campaign with numerous WW2 aircraft and it should blossom. "Build it and they will come."

Turn off MSAA and just use SSAA x1.5

The animation in the pit will most likely be accurate but the axes themselves will be like every other aircraft. There will be no "G-stick", unless ED has a special options function that will cater to FSSB users.

Would rather them just remove it, and the old F/A-18C model already. And whenever the new standard of carriers is released, remove the Stennis as well. Hopefully the Nimitz module will be a platform upgrade that is both freeware and payware. The default should be set as CVN-68 Nimitz and can switch liveries of CVN's 68-77. Edit: I forgot about the large number lighting on the island for night time. That would require a different model for each CVN. I hope they do all 68-77.

You probably just created more bugs downgrading and then re-upgrading. Nonetheless, instead of downgrading you should of tried reinstalling the NVIDIA or AMD video driver first!

Use a proper code editor like Notepad++. It's color-coding helps identify typos. https://notepad-plus-plus.org/download/v7.6.6.html

Shouldn't be a ; at the end of the main API commands sceneAPI:setSky(true) sceneAPI:setCirrus(true) m means nothing. It is just a name variable and can use anything. You could use f14, tomcat, tcat, etc. You missed a , and : instead of . scene.m = sceneAPI:addModel("f-14b", -1.0, 0.5, 4); scene.m.transform:setOrient(0, 270, 0); scene.m:setLivery("VF-143 Pukin Dogs CAG", "f-14b"); scene.m:setArgument(0, 1); scene.m:setArgument(3, 1); scene.m:setArgument(5, 1); scene.m:setArgument(4, 0.25); scene.m:setArgument(6, 0.25); scene.m:setArgument(115, 1); scene.m:setArgument(116, 1); scene.m:setArgument(117, 1); scene.m:setArgument(7, 0); scene.m:setArgument(8, 1); scene.m:setArgument(38, 0.9); scene.m:drawToEnvironment(true); scene.m2 = sceneAPI:addModel("fa-18c", -1.0, 0.5, 12); scene.m2.transform:setOrient(0, 270, 0); scene.m2:setLivery("VFA-131", "FA-18C_hornet"); scene.m2:setArgument(0, 1); scene.m2:setArgument(3, 1); scene.m2:setArgument(5, 1); scene.m2:setArgument(4, 0.25); scene.m2:setArgument(6, 0.25); scene.m2:setArgument(115, 1); scene.m2:setArgument(116, 1); scene.m2:setArgument(117, 1); scene.m2:setArgument(8, 1); scene.m2:setArgument(38, 0.9); scene.m2:drawToEnvironment(true);For a cleaner code example than a bunch of posts on the forum, see my post from a few months ago - https://forums.eagle.ru/showpost.php?p=3659691&postcount=55

I thought it used to be possible but seems to no longer be. Theoretically, it should be possible to take a number of liveries (lets say 10) that all share a few textures. You can create a master livery to serve as a common/base and throw all the common textures into that folder and use "false" in the description LUA of that livery. Now, for the last 9 liveries, all you should need is the unique texture for that specific livery (let's say different tail colors) in the corresponding folder and then use "true" in the description LUA for every common texture used and only use "false" for the unique texture. Doing so should tell the simulator to reference filenames of textures sitting in a different livery. But it doesn't. The only way to accomplish this is by making a standalone module and "mounting" the liveries and texture zips; OR the texture called needs to be inside the Hornet CoreMods FA-18C.zip This is a technique to down-size a large collection of similar liveries and I thought it used to be possible but appears to no longer be both with ModelViewer2 and DCS 2.5. Here is an example with 4 liveries. Livery 1 is the master and 2-4 are supposed to pull Texture #1 from Livery 1 but they don't. Feel free to test. https://www.dropbox.com/s/ws8vhipbwk4dpys/White%20Hornet%20Example%20Mod.zip?dl=0

Dropbox for squadrons wouldn't be nearly as long as the current scheme list for people with a lot installed and is easier and quicker to add than a search box.