Decreasing Loading Times - Back to old GUI

[Invisibull]

lua-gui5.dll is a valid Win32 application, im using XP32bit

 

I don't doubt it's valid. My only concern is that I'm getting an error message and the program won't run. Do i need the 64 bit version of that .dll, or does it matter?

[HungaroJET]

I don't doubt it's valid. My only concern is that I'm getting an error message and the program won't run. Do i need the 64 bit version of that .dll, or does it matter?

 

Yes, i guess. Ask someone (who uses Win7 Pro 64 too) to send you a Beta4 lua-gui5.dll !

Maybe it will work for you also.

[Zorg_DK]

didn't work on the 64-bit exe or the x86 exe, so I reverted back.

[asparagin]

I get this error when loading loading a mission:

 

 

It can be clicked away, but just to let you know..

[HungaroJET]

I get this error when loading loading a mission:

 

It can be clicked away, but just to let you know..

 

Sry, im using XP32 bit, i deleted Win7 coz i had plenty problems with it.

 

but try to ignore row 166 (with two minus signs at the beginning of the row) in me_openfile.lua

(...\DCS A-10C Final\MissionEditor\modules folder)

like this:

-- descriptionWindow:updateWidgetsBounds()

[Kenan]

I suggest this be made a sticky thread at least untill an official patch addresses this (among fair number of users) common issue.

[Invisibull]

OK H-jet, it worked with the 64bit version of the file. Thanks for your trouble. I only hope someone equally as clever can sort out the stutter issue as well. :)

 

Best,

Bull

[ScEBlack1]

Can someone post the 64bit version for those who need it and dont have it? thanks.

[HungaroJET]

Ooops ! :(

Side effect: no descriptions/notes over grids in LOADOUT EDITOR (cursor over weapon)

Tomorrow i will try to fix...

[Grimes]

Will give this a try as the beta 4+ editor has been driving me nuts.

[Kenan]

Ooops ! :(

Side effect: no descriptions/notes over grids in LOADOUT EDITOR (cursor over weapon)

Tomorrow i will try to fix...

 

You mean the tooltips telling you the name of the payload when you put your mouse over it? It works for me.

 

?

[Grimes]

I also need a 64bit lua-gui5.dll. Can a download link be provided?

[asparagin]

Sry, im using XP32 bit, i deleted Win7 coz i had plenty problems with it.

 

but try to ignore row 166 (with two minus signs at the beginning of the row) in me_openfile.lua

(...\DCS A-10C Final\MissionEditor\modules folder)

like this:

-- descriptionWindow:updateWidgetsBounds()

 

Yep, that fixes that. :thumbup:

About the tooltip, you're right, I can't see it.

[sam777777]

hmm, I am getting the error:

[string".\mission editor\mission editor.lua"]:872: attempt to call field ? (a nill value)

 

probably my mistake, seeing as others have got this working, but I have checked that line and even when reverted to original I am still getting the error... :huh:

[greenhut]

Another request for 64bit lua-gui5.dll from beta4 please.

 

Or please email to greenhut AT pobox DOT com

 

thanks!

[Chizh]

Loading time:...........to start screen (launcher.exe)...........to InGameOPTIONS

Beta2 & DCSBS & FC2............~15sec............................. .....~3sec

Beta3.................................~21sec...... ............................~3sec

Beta4.................................~73sec...... ............................~70sec

Final ?!?:.............................~120sec................................~70sec Sinclair ZX Spectrum ?

 

I can't understand what is your problem.

 

I did a fresh installs of A-10C b4 and A-10C release to the Win 7 64 and gaging a time.

After several tests I can confidently say that a load time in beta 4 and release is the same.

 

System: Core 2 Duo E8500, 4 Gb DDRII, NV GTX480.

Loading GUI - 13 sec in the both cases.

Loading Options window - 4 sec in the both cases.

Edited February 28, 2011 by Chizh

[Kenan]

^^His case is not isolated one. There were/are lots of folks (including me before I used HJ's tip) who had serious issues with loading times.

 

Someone mentioned it could be memory leakage related, whatever it is, it is affecting quite a few people and my hope is, it's gonna be addressed in some future patch, not so much because of me and other "know-hows" who are following the forum and can do the edits by themselves (by following instructions) but for less active forum members who are not aware of the fix and are struggling with the above mentioned problem.

[Chizh]

^^His case is not isolated one. There were/are lots of folks (including me before I used HJ's tip) who had serious issues with loading times.

What I have to do that get a your load time digits?

[Boberro]

Old GUI eats a lot less resources and is faster - before I couldn't even run ME, going to Options took ages. Changing to old GUI helped a lot ^^

Overall old gui eats in my case about 400 MB of RAm, new about 700-800. It is big difference.

[Blaze]

Also a request for the 64bit lua-gui5.dll from beta4. :)

[Chizh]

Old GUI eats a lot less resources and is faster - before I couldn't even run ME, going to Options took ages. Changing to old GUI helped a lot ^^

Overall old gui eats in my case about 400 MB of RAm, new about 700-800. It is big difference.

Yes.

New GUI based on the DirectX and a bit less optimised as yet.

 

The main reason for more memory usage is the big DX map from simulator.

In the old OpenGL GUI used a special ME map that was lighter but without accuracy. In the A-10C ME used new common F10 and ME map, therefore you can set any unit in the ME precisely and it can born in the simulator exactly in the same place. But it is used more memory.

Edited February 28, 2011 by Chizh

[NRG-Vampire]

Yes.

New GUI based on the DirectX and a bit less optimised as yet.

 

The main reason for more memory usage is the big DX map from simulator.

In the old OpenGL GUI used a special ME map that was lighter but without accuracy. In the A-10C ME used new common F10 and ME map, therefore you can set any unit in the ME precisely and it can born in the simulator exactly in the same place. But it is used more memory.

 

OK, and any benefits with the new GUI more ?

Coz im not a seriuos mission-maker-man, so i dont really need the exact "you can set any unit in the ME precisely and it can born in the simulator exactly in the same place" thing.

Nice, i can understand the development but needs too much RAM as i see, and needs lots of loading time for 32 bit users i guess :cry:

I see it so, these troubles come forward in 32bit systems with insufficient RAMs, less than 4GB.

 

Now with the old GUI iv got the Beta2 loading times back, just like you Czich with your "final" ! 15sec to GUI, 3sec to Options Window !

Edited February 28, 2011 by NRG-Vampire

[Kenan]

What I have to do that get a your load time digits?

 

Purchase my rig? :D

 

I don't know, but as I said, it's not only me.

Here are my system specs:

 

Windows XP 32bit

AMD Athlon II X2 250 (2x3ghz)

4gb RAM

Ati Radeon 4770 (512mb RAM)

Latest DirectX 9c

[MikeSinn]

What I have to do that get a your load time digits?

 

Chizh

 

I was experiencing the same long load times as others before applying the fix to use the old gui. I however kept copies of the original lua files can can easily roll back and forth between GUIs. I also still have beta4 installed Is there a logging option I can activate and capture the difference in a log file? Is there another info or diagnostics I could send that would help identify the problem?

 

For reference, my system specs are as follows

Intel core duo 2.7GHz

4 GB ram

ATI 5570

Win 7 64 bit

[Grimes]

I had similar load time issues with the new GUI vs the old.

 

System Specs

Intel i7 920 @ 2.63 Ghz

6 gb DDR3

Ati 5770

Win 7 64bit

 

The main reasons I switched back to the old editor are simple.

1. Initial loading time and response time in the editor is much quicker

 

2. I can alt-tab freely between different applications near instantaneously. I have a 2 monitor setup, with old gui I can alt tab to edit a text document on the other monitor while leaving the editor fullscreen on the primary monitor. Alt-tabbing in new gui (with and without full screen checked in options) minimizes the editor and takes considerable time to reload back in. New GUI is also crash prone when attempting to re-enter the application.

 

3. Going from simulator to editor is much quicker and less crash prone in the old gui.