Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 2 3 [4] 5 6 7 ... 33   Go Down

Author Topic: MiG-21 Pack V 4.1 - 30.09.2018  (Read 127823 times)

0 Members and 1 Guest are viewing this topic.

SAS~Tom2

  • SAS Honourable Member
  • member
  • Offline Offline
  • Posts: 7954
  • no sweat
Re: MiG-21 Unified Pack
« Reply #36 on: September 29, 2015, 02:10:53 PM »

I will try to write one tomorrow! ;)
Logged

4S_Vega

  • Modder
  • member
  • Offline Offline
  • Posts: 3748
Re: MiG-21 Unified Pack V.1.1
« Reply #37 on: September 30, 2015, 11:00:27 AM »

new link at first post

there are also advices for installation
Logged

Vlada SD

  • member
  • Offline Offline
  • Posts: 19
Re: MiG-21 Unified Pack V.1.1
« Reply #38 on: September 30, 2015, 11:03:23 AM »

What is new?
Logged

4S_Vega

  • Modder
  • member
  • Offline Offline
  • Posts: 3748
Re: MiG-21 Unified Pack V.1.1
« Reply #39 on: September 30, 2015, 11:29:45 AM »

there is some bug fixed compared to the initial version released yesterday
Logged

SAS~Tom2

  • SAS Honourable Member
  • member
  • Offline Offline
  • Posts: 7954
  • no sweat
Re: MiG-21 Unified Pack V.1.1
« Reply #40 on: September 30, 2015, 01:01:16 PM »

Thanks Vega!

Logged

SAS~Tom2

  • SAS Honourable Member
  • member
  • Offline Offline
  • Posts: 7954
  • no sweat
Re: MiG-21 Unified Pack V.1.1
« Reply #41 on: September 30, 2015, 01:30:22 PM »

A tip for new to modded IL-2 users:

The basic mods you must have are listed in the first post:
E.g. The Jet Era mod, for a 4.12 install with Mod Act 5.3 (See the ModAct forum area on how to install ModAct 5.3) you do not need to add any of the RC entries. Follow the procedure for 4.12 mentioned here:

https://www.sas1946.com/main/index.php/topic,15649.0.html

IIRC I did not even add any RC or other lines, just the ini and plane/weapons etc. entries.


In C.U.P. the Jet Era is already part of the Jet module.

Now to more basic stuff:
If an instruction tells you to add an ini file entry, you first navigate to the folder that contains the "STD" folder parent:

In Mod Act 5.3 this would be:
IL-2 Sturmovik 1946\#SAS

Your #SAS named folder is also where all the new mods go (or for other installs your Mods or #UP# folder) except directed otherwise by the modder (e.g. a JSGME mod).
Even a JSGME mod, once you are a bit more used to modding your game, can be extracted manually BTW if you follow its folder conventions.

Back to the STD folder:

If you read:
To install, add to:
"air.ini", followed by entries, usually marked in code, then you simply open:
IL-2 Sturmovik 1946\#SAS\STD\com\maddox\il2\objects and there the air.ini file.


Open it e.g. with notepad and, important: Before you make any changes inside the STD folder, BACKUP the entire bitch!!

So...you open the air.ini file and add the entries as mentioned in the install instructions.
Exactly as there, no changes.

Then you look what is next (No particular order required)
Plane means the former (Pre 4.12 installs like 4.10/4.09m) plane_ru.properties named file:

You open:
IL-2 46Basicbackup\IL-2 Sturmovik 1946\#SAS\STD\i18n  and there:
plane.properties

Add the needed text lines and save, like with the air.ini.


If there is a weapons entry needed:

Open IL-2 46Basicbackup\IL-2 Sturmovik 1946\#SAS\STD\i18n/weapons.properties

And add the changes.


Where you add such entries does not really matter to my knowledge, but make sure you enter such data the way it is named by the modder and make no typos, always best to copy and paste these lines of course.


Now if you have a static, technics, stationary etc entry, do the same as above and find those files again inside:

IL-2 46Basicbackup\IL-2 Sturmovik 1946\#SAS\STD\com\maddox\il2\objects


For technics.ini and static.ini as well as stationary and all other inis as air.ini, make sure to not enter new lines below the // eof marker.


E.g. for the static.ini, all my entries go above

//==========================================================================
// eof
//==========================================================================




That si the very basics, the rest is mentioned in the newbie forum section.

Make sure to not overwrite entries and add them like the modder named them. ;)
And pray he knows what he is doing.. :P :D I always copy my entire STD folder to a safe place anytime I make a change. As backup of course. :P



BTW for air.ini entries I always make sure to not add anything in or below the "placeholder" section. And it is a good manner to add new entries in the vincinity of similar planes, e.g. Mig-15s/17s or similar era planes.

Good Luck gentlemen.. ;) It is not difficult, only takes some patience.

Logged

SAS~Tom2

  • SAS Honourable Member
  • member
  • Offline Offline
  • Posts: 7954
  • no sweat
Re: MiG-21 Unified Pack V.1.1
« Reply #42 on: September 30, 2015, 01:38:40 PM »

For those who want more help, here is another example of how to install a plane:

https://www.sas1946.com/main/index.php/topic,35719.0.html



Frankly, from time to time I mess up my install as well, that is why I always backup. Sometimes even a good install method will go wrong if there are bugs in a new mod. The more complex the mod the easier something can go wrong, and the Migs are quite complex, but not rocket science. That means if we guys can do it, you guys can do as well. :)  ;)
Logged

Yaroslav

  • member
  • Offline Offline
  • Posts: 13
Re: MiG-21 Unified Pack V.1.1
« Reply #43 on: September 30, 2015, 05:37:51 PM »

tested sas md 4.12.2 this is awesome machine, thanks!!!! beautiful ;)
Logged
BBC POCC

SAS~Tom2

  • SAS Honourable Member
  • member
  • Offline Offline
  • Posts: 7954
  • no sweat
Re: Mig-21PFM blown flaps issue
« Reply #44 on: September 30, 2015, 05:38:40 PM »

Tested:

All inis deleted, added these:

Air.ini

    MiG-21FL   air.MIG21FL            NOINFO   r01 SUMMER
    MiG-21PF   air.MIG21PF            NOINFO   r01 SUMMER
    MiG-21PFM   air.MIG21PFM            NOINFO   r01 SUMMER
    MiG-21S           air.MIG_21S                           NOINFO  r01   SUMMER
    MiG-21R           air.MIG_21R                           NOINFO  r01   SUMMER
    MiG-21MF         air.MIG_21MF                         NOINFO  r01   SUMMER
    MiG-21bis         air.MIG_21bis                         NOINFO  r01   SUMMER



stationary.ini

    MIG_21PF             vehicles.planes.MiG21Static$MIG21PF 1
    MIG_21PFM             vehicles.planes.MiG21Static$MIG21PFM 1
    MIG_21FL             vehicles.planes.MiG21Static$MIG21FL 1
    MIG_21S             vehicles.planes.MiG21Static$MIG_21S 1
    MIG_21MF             vehicles.planes.MiG21Static$MIG_21MF 1
    MIG_21bis             vehicles.planes.MiG21Static$MIG_21bis 1


plane.properties

    MiG-21PF  MiG-21PF Fishbed-D, 1961
    MiG-21PFM  MiG-21PFM Fishbed-F, 1964
    MiG-21FL  MiG-21FL Fishbed-D (Export), 1965
    MiG-21S   MiG-21S Fishbed-J, 1964
    MiG-21R   MiG-21R Fishbed-H, 1965
    MiG-21MF  MiG-21MF Fishbed-J, 1970
    MiG-21bis  MiG-21bis Fishbed-L, 1972





Issue:
At landing, as soon as blown flaps are active, heavy pitch up momentum, if you counteract it by pulling down the nose:
Explosion.



I took two records in the Crimea map, one longer with the takeoff in pairs Scramble Mission:


A complete medium long performance ride and as I wanted to land the explosion with blown flaps.
https://www.mediafire.com/download/2r620dzrj6rtrzy/For+Vega.rar


A record with the default takeoff Crimea mission:
https://www.mediafire.com/download/uy4093m394isn76/For+Vega+default+Scramble+blown+flaps+issue%282%29.rar


Logfile

https://www.mediafire.com/download/ab5pd2wg7a477d8/log.rar


Otherwise nice. :P  :) :P
Logged

Whiskey_Sierra_972

  • Modder
  • member
  • Online Online
  • Posts: 6166
  • In memory of my beloved hero: Saburo SAKAI!
Re: MiG-21 Unified Pack V.1.1
« Reply #45 on: October 01, 2015, 12:05:03 PM »

Hi mates!

Apologize for the delay in installing and testing but I got a lot of work in the last days!

Anyway....

Installed and got all working flawless....almost all....

The only issue I got is with the stationary planes:

The Technics entries are needed to show the plane but when added only the Late MiGs are showing correctly while the Early MiGs don't....and the R variants is missing (not sure if left out or forgotten)....

Here is the log for PF and FL that simply don't show afetr clicking on the 'SHOW' buttons....while the PFM should have some other issue because the option 'SHOW' isn't neither available....

Code: [Select]
nulljava.lang.RuntimeException: INTERNAL ERROR: HierMeshObj: Can't load HIM

at com.maddox.il2.engine.HierMesh.Load(Native Method)
at com.maddox.il2.engine.HierMesh.<init>(HierMesh.java:596)
at com.maddox.il2.engine.ActorHMesh.setMesh(ActorHMesh.java:89)
at com.maddox.il2.engine.ActorHMesh.<init>(ActorHMesh.java:111)
at com.maddox.il2.objects.ActorSimpleHMesh.<init>(ActorSimpleHMesh.java:26)
at com.maddox.il2.builder.WSelect.setMesh(WSelect.java:149)
at com.maddox.il2.builder.WSelect.setMesh(WSelect.java:119)
at com.maddox.il2.builder.WSelect$3.notify(WSelect.java:227)
at com.maddox.gwindow.GWindowDialogControl._notify(GWindowDialogControl.java:51)
at com.maddox.gwindow.GWindowDialogControl.mouseClick(GWindowDialogControl.java:86)
at com.maddox.gwindow.GWindow._mouseButton(GWindow.java:556)
at com.maddox.gwindow.GWindowRoot.doMouseButton(GWindowRoot.java:251)
at com.maddox.gwindow.GWindowManager.doMouseButton(GWindowManager.java:69)
at com.maddox.il2.engine.GUIWindowManager.msgMouseButton(GUIWindowManager.java:126)
at com.maddox.rts.MsgMouse.invokeListener(MsgMouse.java:98)
at com.maddox.rts.Message._send(Message.java:1217)
at com.maddox.rts.Message.sendToObject(Message.java:1191)
at com.maddox.rts.Message.sendToArray(Message.java:1147)
at com.maddox.rts.Message.sendTo(Message.java:1128)
at com.maddox.rts.Message.trySend(Message.java:1115)
at com.maddox.rts.Time.loopMessages(Time.java:180)
at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:101)
at com.maddox.il2.game.MainWin3D.loopApp(MainWin3D.java:131)
at com.maddox.il2.game.Main.exec(Main.java:449)
at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)
nullnulljava.lang.RuntimeException: INTERNAL ERROR: HierMeshObj: Can't load HIM

at com.maddox.il2.engine.HierMesh.Load(Native Method)
at com.maddox.il2.engine.HierMesh.<init>(HierMesh.java:596)
at com.maddox.il2.engine.ActorHMesh.setMesh(ActorHMesh.java:89)
at com.maddox.il2.engine.ActorHMesh.<init>(ActorHMesh.java:111)
at com.maddox.il2.objects.ActorSimpleHMesh.<init>(ActorSimpleHMesh.java:26)
at com.maddox.il2.builder.WSelect.setMesh(WSelect.java:149)
at com.maddox.il2.builder.WSelect.setMesh(WSelect.java:119)
at com.maddox.il2.builder.WSelect$3.notify(WSelect.java:227)
at com.maddox.gwindow.GWindowDialogControl._notify(GWindowDialogControl.java:51)
at com.maddox.gwindow.GWindowDialogControl.mouseClick(GWindowDialogControl.java:86)
at com.maddox.gwindow.GWindow._mouseButton(GWindow.java:556)
at com.maddox.gwindow.GWindowRoot.doMouseButton(GWindowRoot.java:251)
at com.maddox.gwindow.GWindowManager.doMouseButton(GWindowManager.java:69)
at com.maddox.il2.engine.GUIWindowManager.msgMouseButton(GUIWindowManager.java:126)
at com.maddox.rts.MsgMouse.invokeListener(MsgMouse.java:98)
at com.maddox.rts.Message._send(Message.java:1217)
at com.maddox.rts.Message.sendToObject(Message.java:1191)
at com.maddox.rts.Message.sendToArray(Message.java:1147)
at com.maddox.rts.Message.sendTo(Message.java:1128)
at com.maddox.rts.Message.trySend(Message.java:1115)
at com.maddox.rts.Time.loopMessages(Time.java:180)
at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:101)
at com.maddox.il2.game.MainWin3D.loopApp(MainWin3D.java:131)
at com.maddox.il2.game.Main.exec(Main.java:449)
at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)
[Oct 1, 2015 6:06:08 PM] -------------- END log session -------------

All other aspect are really good even if about landing behaviour I can't help because for me is still an hard plane at landing due my limited skills....

Thanks for the hard work and the lot of time all you expend behind this great project from the initial releases to this last Unified Pack!!!
Logged

Seb

  • Modder
  • member
  • Offline Offline
  • Posts: 555
Re: MiG-21 Unified Pack V.1.1
« Reply #46 on: October 01, 2015, 12:13:43 PM »

Landing MiG-21 was in fact very difficult to which was due to the small span of the wings at the heavy weight airplane, forcing a high speed during landing.
Include movie from landing MiG-21 on the highway which trained Polish pilots.
When a little practice landing is not as difficult as Vega advises should be approached for a landing with 70% power with releases on flaps and brakes.
Seb

Logged

SAS~Tom2

  • SAS Honourable Member
  • member
  • Offline Offline
  • Posts: 7954
  • no sweat
Re: MiG-21 Unified Pack V.1.1
« Reply #47 on: October 01, 2015, 12:20:33 PM »

Walter:

I think there is no stationary R version added, that is normal AFAIK.

For landing:
I have to say it is really difficult, but blown flaps should add more help. The trick is to hit the runway just when the lift drops and not bounce off again, TBH (also due to an issue I had with flaps) I could only land once without exploding.

Apart a so far unique issue I have in my install, these Migs fly really immersively.
Will later add the alternative cockpit colour options as add on.
Logged
Pages: 1 2 3 [4] 5 6 7 ... 33   Go Up
 

Page created in 0.099 seconds with 21 queries.