Flyable Su-30 with Su-27 6DOF cockpit

[zaelu]

I solved the problem

 

adding this "OPTIC = "Shkval"," to my Su-30.lua crashed the game pronto.... maybe because my other mod lua (human blah blah) was not making Su30 a Su25T type plane...

 

But that shows how touchy the game is :D .

 

 

My tracker never works with Su30... that's a given... I can't solve it for now but...

 

My radar capabilities seems to elude me... Is there some one else that figured it out how to make radar work? What triggers the normal radar to work.?..

 

I solved the radar... I was just moronic... or I had drink to much beer or something... I was testing it on the ground... :D

 

Anyway... I touched the mod a little:

 

 

Also Evilducky, I attached my "side of files"... lua etc. If you have time could you look into them and see if you observe something that may cause the fact that I have no head tracking in Su30?

 

I excluded from my attach Combatace Bazar files (3d model etc) and EDs SU27 cockpit model (EDM file) and cockpit textures archive.

I included the Pylons and Customhuman luas files that were coming with Combatace original mod in scripts folder.

Also I included a folder Su30 Themes and the files that make the mod appear like in the screenshot above... all my modifications are made in "Entry.lua" file and adding that folder with pictures.

Edited May 17, 2013 by zaelu

[Stratos]

Does this mod really add a proper Su30 with usuable guided A-G weapons and at the same time A-A missiles?

[ericoh]

Yup. Flaming Cliffs guided weapons that is. Do not expect A-10C Systems.

[Evilducky]

Zaelu I didn't see you edited your post. Ill take a look at that stuff for ya sometime soon. I also made my own background and icon and music, but I think ill be snagging your icon as its way better than mine :-P.

 

I've been reading through a ton of codes to try and get something special worked out for you guys but I'm not having any luck finding that I need. Oh well. :-P

[zaelu]

As I said to you I made several "testings" with other planes... namely... F15E, F16C and F18C. For all I tried to use them as F15C and with F15C 3D cockpit.

 

-with F15E I had the most success. I got it to work with F15C cockpit and to have head tracking... but no weapons would work on the plane as the game crashed immediately after trying to enter the plane. It may be a problem with just some weapons but I couldn't test all yet.

-with F16C I had F15C old 2D cockpit and head tracking but no input whatsoever... i couldn't close the canopy or start the engine...s :) But I could attach weapons on it without crashing the game.

-with F18C (the one I wanted the most actually) I had the least success. The F15C 2D cockpit was all I could get, But no head tracking... only mouse look. Weapons can be attached to it and the controls are in general working.

 

from what I observed:

 

There is no need to modify /scripts/database/planes/plane_name.lua. Those luas contained a line that said human controllable but I think is ignored now by the game and most of the moded files don't have it anyway. All the mods are adding there are customized load outs... which is not necesary to make them to fly by human.

 

Modifying the /scripts/aircrafts/_common/CustomHuman.lua makes the plane behaving as a certain already flyable plane... if you say Su30 is like a Su25T it will behave like one in avionics (not sure about flight model, didn't tested) but you (I think) need to have in Mods/aircrafts/Su30 (for example) folder the Input folder that contains copies of default Su25T input folder and in C:/Users/user_name/saved games/DCS/Config/Input/ you must have same Su25T controls or delete previous so the Su25T gets written there (this is not yet tested). This way you should have lasing and target size etc controls.

 

If you don't modify that customhuman.lua I think Su33 cockpit will be used by default if the plane is make flyable via "Mods/aircrafts/moded plane/ folder files... namely the "entry.lua". Editing the customhuman.lua force the game to put to the moded plane not only the said plane characteristics but also the default cockpit if no cockpit is provided in mods folder... hence some of my problems I think...

 

- Also... it appears that the problems of correct cockpit and headtracking are related with naming correctly the plane. I was just lucky with F15E cause that is the name of the plane for game engine. But for F18C is F/A-18C or FA_18C... ad that / cannot be put in the name of a file... as the name of the cockpit edm or textures archive... The F16C as an even more complicated name... something with bl52C and is called sometimes with F16-C2 etc... a real joy :D.

 

I'm saying this that maybe you guys have different ideas. I put those 3 planes in a folder inspired by "flaming cliffs" folder from Mods and I name it X Control so it will be the last module all the time. I''l upload here my lua edits so you can play with them if you wish.

 

I added an archive containing a folder structure and some luas that will insert a "mod" named "x control" in your game. You may play with it as you like and add whatever plane you like to it. Please leave feedback so maybe more problems will be solved. It contains a readme with instructions. I compacted it into one mod so maybe intime we add more and more planes and we should not have more buttons than necessary and we can disable it quickly.

 

Does not contain files of 3d cockpit or textures that are made by ED. Just luas and sme pictures so the mod has icons and a background picture. It looks like this:

 

:)

Edited May 20, 2013 by zaelu

[Evilducky]

Im still standing on my grounds of saying be careful of editing the Customhuman.lua file as it seems to do strange things with any flayable aircraft mod (it was what was causing issues with my radar not working and the inputs not working if you remember from my other post on it). If you were to look at the mod I originally posted here there is no modification to the customhuman.lua file and the plane works just fine as the Su-30 with the Su-27 cockpit and controls. Just an FYI

[zaelu]

Yes, not only it changes the behavior of the plane with the one specified in customhuman.lua but also the HUD and functions... and you need input folder from that plane you instructed the game to be other wise you will get messed up controls etc. check PM :)

[zaelu]

LOL, I found out how to put the F15C 3D 6DoF cockpit on new F18C model... but I still don't have Tracking.

 

I had observed the followings:

 

If naming of the texture/model file or the instruction in entry.lua is incorrect the cockpit will default automatically to the 2D one that is specified in CustomHuman.lua. If nothing is specified there at least the HUD defaults to a Su27/33 one. The HUD will default to a russian one if you have named the cockpit model files and line in entry.lua correctly but failed to specify in CustomHuman.lua with what to resemble the avionics of the moded plane.

 

The naming can be tricky... for F18C I solved it (I laughed at the solution...) but for F16C... is dificult and not yet solved... I think I'll go for A model cause it's simpler and anyway looks like crapola for these days.

 

Also... If F15E or Tornado is set in CustomHuman.lua to be like F15C they will have limitation to 11 pylons... that's why it was crashing upon joining the planes cockpit.

 

A. L-39ZA, F16C have a problem at using the input folder... no matter what I set for them in controls... nothing works... for now.

B. MiG31, Su30, F18C work almost completely but no head tracking

 

From these to lines (A and B) I observed that if a plane cannot somehow "read" the Input Folder they will have by default headtracking but when they can read and modify the input folder and accept controls then headtracking dissapears.

MiG 31 and F18C refused controls at the beginning but after clearing the problem and making the input folder folder work the head tracking disappeared. Although the files inside the headtracking and Trackir folders are identical with the ones in F15E that works flawlessly.

 

If anyone else has some other ideas...

Edited May 22, 2013 by zaelu

[Evilducky]

What did you have to put around for the F18C to work? I tried to get that one to work the other day with no luck on getting the 3D pits to work.

[SkateZilla]

at one point i used the F-15C pit w/ all avionics to play with the F-18C, everything worked except A2G stuff obviously, so You can take the hornet and fly Air To Air w/ Aim9s and 120s,

 

Im in my office, so i dont have access to files.

 

But you need to specify the F-18Cs WSTYPE and then link it to the F-15c's avionics.

 

so in CustomHumanLUA for example, needs to have something like.

 

CustomHumanData[PlaneType.F_18C ] = CWSType.iCWS_F_15

 

 

 

Dunno if it's changed with recent builds, but you should be able to drop the Cockpit EDM into the Shapes folder and give it a specific name and it will automatically load it without being specified in the LUA's

 

ModuleName-CPT for example.

Edited May 22, 2013 by SkateZilla

[zaelu]

The problem is the naming... For example the F16C is called F-16C bl.52 or so... and this screws all in regard of naming paths and files... or at least I couldn't do it...

 

But... with F18C... great succes! It took a bit of overclocking of "lateral thinking module" and it worked. :D

 

F18C is called: F/A-18C, but you can't name a file with / or \ character... But... this is the name you need to "declare" when making it flyable in entry.lua and the lines for making the cockpit you wish to place in "Shapes" and "Textures" folders that may be the F15C 3D one with 6DoF or any other has to be like this:

 

mount_vfs_texture_path (current_mod_path .. "/Cockpit/Resources/Model/Textures/F/A-18C-CPT-TEXTURES")

 

mount_vfs_model_path (current_mod_path .. "/Cockpit/Resources/Model/Shape/F")

 

make_flyable('F/A-18C' , current_mod_path..'/Cockpit/KneeboardRight/', nil, current_mod_path..'/Comm/F-18C.lua') --note that only the first part make_flyable('F/A-18C' , is mandatory the rest you may write it as you please as long as it works.

 

And the files paths should be like this:

 

The EDM 3D cockpit

 

\DCS World\Mods\aircrafts\X Control\Cockpit\Resources\Model\Shape\Cockpit_F\A-18C.EDM

 

Yes the file is called: A-18C.EDM and is placed in a sub folder named Cockpit_F... if you look above you realize why :lol:

 

The Texture

 

\DCS World\Mods\aircrafts\X Control\Cockpit\Resources\Model\Textures\F\A 18C-CPT-TEXTURES.zip

 

The same applies... The archive is named A 18C-CPT-TEXTURES.zip and it is placed in a sub folder named F... for obvious reasons now :D

 

Note that the folder X Control is just the folder that holds my Mod... if you wish to make it just for F-18C you may name that folder F-18C or anything you wish. You may also insert all edits in Entry.lua from Flaming Cliffs folder... you get the idea...

 

 

The result will look similar to this but it is recommended you copy the section regarding cockpit view point etc of F15C from your "server.lua" in config\view and start editing the position of the cockpit until fits your preferences.

 

Also you may create section for F/A-18C in defaultsnapviews.lua and your snapviews.lua and edit them as you like.

 

Edited May 22, 2013 by zaelu

[Stratos]

And you can use A-A and A-G weapons on it?

[zaelu]

A-A for sure... A-G... only if you make it act like a A-10A or some A-G russian plane... but you lose radar and most a-a missiles

[SkateZilla]

The problem is the naming... For example the F16C is called F-16C bl.52 or so... and this screws all in regard of naming paths and files... or at least I couldn't do it...

 

I can guarantee you the F-16C is not listed as "F-16C Bl.52" under the WSType chart. and the F-18C is not listed as F/A-18C either.

 

Those are folder path/module names.

 

Those can be changed in the LUA as well.

Edited May 22, 2013 by SkateZilla

[zaelu]

It didn't work other way.

 

But do you have any idea why headtracking works only on some of the moded planes? Also inputs don't work... for L-39ZA for example... or F-16.

[SkateZilla]

Inputs how? as in Flight Controls?...

 

Headtracking will prolly work on the F-15C Pits.

 

I'd have to look at the Mod as a whole and see how you set it up.

Edited May 22, 2013 by SkateZilla

[SkateZilla]

under:

type = "F/A-18C"

 

that should be the WSType i think

 

So:

type=FA_18C or F_18C

 

I'll take a look at it this weekend, but like I've said before Im not for making "free flyables" out of ED's assets.

 

But, I'll see how I have it setup on my end,

 

Im pretty sure I individualized the module and designated it to use the ingame F-18C assets already, then just scripted CustomHuman to Set_ the F-18C to use the F-15C Pit and stuff.

Edited May 22, 2013 by SkateZilla

[SkateZilla]

Edit; nevermind

[zaelu]

I will give it a try... in the mean time I recreated the original DDS files for Combatace missiles models that had no MIPs and looked jaggy from distance... if anyone wants them I could upload them on dropbox.

 

The missiles are CombatAce work I just resaved them... 2 minutes job... so they will not look jaggy when view from few meters away.

 

 

And I understood what CombatAce meant with first number sets what model is used... with or without canards... it works in DCS World very well.

 

It simple means that when you give a bort number to your plane if you give it from 01 to 79 you get russian version... if you give it 80 to 99 you get indian version with canards. Above 99 I think the middle number sets the model.

 

He is pretty clear here:

 

Please have a look at these screenshots.

 

For Russian plane

 

For Indian Plane

[SkateZilla]

You also dont have all the correct Aircraft names in the \Input\AIRCRAFT\Name.lua

 

Right now I can get the hornet and all it's avionics with the old F-15 pit, dunno why it's not loading the 3d pit.

 

F-18 also has the same gear problem as the F-15

Edited May 23, 2013 by SkateZilla

[Evilducky]

ha! found out something fun today about the 3D pits. When in the cockpit, hit M and watch your mirrors wiggle =P So awesome. :)

[zaelu]

You also dont have all the correct Aircraft names in the \Input\AIRCRAFT\Name.lua

 

Right now I can get the hornet and all it's avionics with the old F-15 pit, dunno why it's not loading the 3d pit.

 

F-18 also has the same gear problem as the F-15

 

Did you had any problem from the beginning with inputs commands ( for example basic close canopy and start engines... etc) and head tracking and you solved it by modifying the names in \Input\AIRCRAFT\Name.lua ?

 

For example My F-18C works without having F/A-18C in \Input\AIRCRAFT\Name.lua stated... but no head tracking.

Also F-16A has Headtracking but no command work except general... F views, Easy radio.

L-39ZA is the same... has head tracking but no inputs work although they appear in options and I can modify them but they are not linked to the actual plane somehow...

 

To get the 3D pit in F-18C try my solution above... it should work.

 

And for the gear... russian ones suffer gear collapse if treated roughly on take off or landing... I broke one MiG31 and it is acting like a Su27 in avionics.

 

ha! found out something fun today about the 3D pits. When in the cockpit, hit M and watch your mirrors wiggle =P So awesome. :)

 

This is impossible!! I was sure this is what it will do and I tried it but it didn't worked for me some time ago... I'll try again today. :D Nice find!

[SkateZilla]

Did you had any problem from the beginning with inputs commands ( for example basic close canopy and start engines... etc) and head tracking and you solved it by modifying the names in \Input\AIRCRAFT\Name.lua ?

 

For example My F-18C works without having F/A-18C in \Input\AIRCRAFT\Name.lua stated... but no head tracking.

Also F-16A has Headtracking but no command work except general... F views, Easy radio.

L-39ZA is the same... has head tracking but no inputs work although they appear in options and I can modify them but they are not linked to the actual plane somehow...

 

To get the 3D pit in F-18C try my solution above... it should work.

 

And for the gear... russian ones suffer gear collapse if treated roughly on take off or landing... I broke one MiG31 and it is acting like a Su27 in avionics.

 

 

 

This is impossible!! I was sure this is what it will do and I tried it but it didn't worked for me some time ago... I'll try again today. :D Nice find!

 

Issue is they all show up in controls as F-15C, lol.

 

So I Adjusted the Names to the Names of the Aircraft.

 

ie, the name.lua in the /F-18 input folder says:

return _('F-15C'), it should be: return _('F-18C') or return _('F/A-18C')

 

There are no Input folders for the F-16A, Only the F-16C, there also isnt any Input folders for the L-39ZA

Edited May 23, 2013 by SkateZilla

[Evilducky]

Soo... apparently my game doesnt want me to fly the F-18 with a 3D cockpit cause I cant get this to work right.. lol. Go me :)

[zaelu]

Yeah... the archive I posted above is older. I know what that lua does... I saw 5 F15C also and figured it out :D but even after naming correctly some planes have no input at all... and that's making them have headtracking and some have all controls working. Some that originally didn't had controls once they got controls lost headtracking...

 

This is one of mysteries...

 

I managed to place F-18C cockpit in such manner you don't see the pilot/cockpit/canopy from external model...

 

it looks like this (for F15C 3D cockpit):

 

ViewSettings["F/A-18C"] = {

Cockpit = {

[1] = {-- player slot 1

--CockpitLocalPoint = {3.570000,1.900000,0.000000}, -- upward but aligned horizontally

--CockpitLocalPoint = {4.600000,1.220000,0.000000}, -- forward but aligned vertically

CockpitLocalPoint = {4.600000,1.450000,0.000000}, -- hybrid but wokable

CameraViewAngleLimits = {20.000000,105.000000},

CameraAngleRestriction = {false,90.000000,0.400000},

CameraAngleLimits = {140.000000,-90.000000,90.000000},

EyePoint = {0.150000,0.000000,0.000000},

limits_6DOF = {x = {-0.050000,0.450000},y ={-0.200000,0.200000},z = {-0.220000,0.220000},roll = 90.000000},

 

Soo... apparently my game doesnt want me to fly the F-18 with a 3D cockpit cause I cant get this to work right.. lol. Go me :)

 

Have you tried my solution above and it didn't worked?

 

 

EDIT

 

I attached a new version of the mod... take a look at the files and see how I did it for F18C and maybe you spot why some controls don't work on my planes or headtracking for F18C and Su30.

 

And sometimes radio commands don't work although the rest work...

X-Control-beta2.rar

Edited May 23, 2013 by zaelu