[Nuke]

i think im going to solve the cockpit problem by having all the cockpit data and scripts in one mod dir, and the base mod in another. so sissies who dont like cockpits / people with performance issues can still run the mod without all the bells and whistles. of course that means cockpit players cant play non cockpit players (who wants to play with them anyway) in multi. having the ability to turn them on and off in the context of the same mod would be awesome though. of course the way they work in my mod is so bizarre that any switch you implement probably wouldn't work

[karajorma]

Yeah. Nukemod is a very good example of the problems this sort of switch could cause. If someone were to play nukemod with the cockpit mod selected and then use a hypothetical launcher option to turn off the cockpits it would probably crap out in a variety of interesting methods.

With the method I'm suggesting however it would be simple. You'd simply set the tables for the mod to tell the game ignore launcher settings and the problem would be averted.

[Nuke]

i dont really consider having cockpits on and off as a balence concern. cockpits are more effective than no cockpit when you use something like the trackir, because your improved situational awareness would suffer from not having an internal reference (your cockpit model). while in your fixed view, the cockpit model would get in your way and there is no need for a reference. i think these situations essentially cancel each other out, and if i had the capacity to make it an optional thing, i probably would. same goes for radar, ive made so many different radars so il just let the user pick their favorite one, most likely with a keyboard command in that case.

[chief1983]

They only cancel out when you have TrackIR, which almost no one does, otherwise the cockpit tends to just get in the way of your view of a target.

[Nuke]

as much as i like my trackir and would hate for it to collect dust while im playing a game that supports it. it could be seen to give an unfair advantage in multiplayer. im not sure if this is true or not, but it might be advisable to have a host option to disable it, so as to make multiplayer more fair. i dont think it makes as much of a difference because of the targeting features you get. still, its something that the game host should get to decide.

[FUBAR-BDHR]

The way I look at it if I'm any good trackir or teamspeak or any other advantage you use just makes it more satisfying when I had you your arse. Now scripted aiming and that kind of stuff can be an issue. 

Reminds me of the time someone modded a beam that took out everything in 5k.  No idea how it got passed table checks but I still won.  Trebs have a range of 5200. 

[Nuke]

i kind of find the trackir difficult to use without the reference that is a cockpit model. without those little bits of cockpit its hard to determine what direction you are looking in if you cant see the reticule. still i dont have much interest in fs2 multiplayer. it always feels like playing vanillia (because it usually is).

making scripts for multiplayer would most likely require some anticheating code on behalf of the scripter, unless of course you keep all your code in the scripting.tbl, which is bad for organizing your scripts and can make for a heavy file. lua does allow you to compile scripts to a binary format, but im not sure if that would help the situation any. you would need to crc all your script files, have some script in the table check the external files and insure the right directory placement against data in the scripting.tbl's lua code. not sure if the engine had any security for external lua files. just something to think about.