Перейти к содержимому
View in the app

A better way to browse. Learn more.

Zloplay community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

Опубликовано:

When I watch my demo,what is not recorded in LEGACY server, it starts at mid game and at almost end it stops and says "Lost connection to host". And also my second demo in oilrig, when I open it the game will crash and multiple mw2 programs pop up. If I can't fix these problems, I have lost a noscope wallbang triple and quad underbarrel :x PLEASE HELP ME!

Опубликовано:

/demoback isn't working..

Опубликовано:

/demo [demoname];wait 5;demoback 1

 

:D

Опубликовано:

I stopped recording when scoreboard came up, before next game

Опубликовано:
I stopped recording when scoreboard came up, before next game

A harrier killstreak might have messed the demo file up.

 

It's not just harriers. Those demo crashes in 'mid-game' seem to be caused by the 'location selector UI' actually.

So the demo will be messed up when using the location selector for airstrike, harrier airstrike or stealth bomber.

 

I played around with _airstrike.gsc and when you remove:

 

self beginLocationSelection( "map_artillery_selector", chooseDirection, targetSize );

 

and define chooseDirection/ targetSize in the .gsc ( so that the actual location selector map doesn't show up when using harrier airstrike etc.) it won't be messing up the demo.

Therefore it's actually the location selector UI which messes up the demos.

  • 3 weeks later...
Опубликовано:
Hello, i dont have any _airstrike.gsc and i dont even know where is it (looked @m2demo/maps/mp/killstreaks)

 

You can't fix already recorded demos by using a modified _airstrike.gsc.

The server would have needed the modified .gsc at the time you were recording.

But then you wouldn't have been able to choose the airstrike location manually. It would just have sent the airstrike to the position specified in the .gsc, without opening the location UI at all.

So what i posted above is not really a 'fix' at all.

 

Oh BTW: I tried the cod4 location ui (the .menu file) in IW4M and it also breaks demos. Therefore i guess that some hard coded location UI related 'stuff' is actually breaking the demos.

Опубликовано:

So far the only solution I've found to avoid having your demos broken are to simply not use any killstreaks that use the UI locaton (Harrier, Precision Strike, Stealth Bomber)

 

And as said above, you can't fix the already broken demos...I've tried long and hard but not results :P

Опубликовано:
just clean up the menu file? Only name and visible 0

 

How would that help? As i said it doesn't seem to be related to the .menu file at all.

( I tried that already and demos still broke. )

 

In fact the call

self beginLocationSelection( "map_artillery_selector", chooseDirection, targetSize );

seems to break demos, whereas the beginLocationSelection(arg1, arg2, arg3); function seems to be hard-coded.

  • 2 weeks later...
Опубликовано:
I stopped recording when scoreboard came up, before next game

A harrier killstreak might have messed the demo file up.

 

It's not just harriers. Those demo crashes in 'mid-game' seem to be caused by the 'location selector UI' actually.

So the demo will be messed up when using the location selector for airstrike, harrier airstrike or stealth bomber.

 

I played around with _airstrike.gsc and when you remove:

 

self beginLocationSelection( "map_artillery_selector", chooseDirection, targetSize );

 

and define chooseDirection/ targetSize in the .gsc ( so that the actual location selector map doesn't show up when using harrier airstrike etc.) it won't be messing up the demo.

Therefore it's actually the location selector UI which messes up the demos.

 

Where can I find the _airstrike.gsc and does it really works?

  • 2 weeks later...
Опубликовано:
I stopped recording when scoreboard came up, before next game

A harrier killstreak might have messed the demo file up.

 

It's not just harriers. Those demo crashes in 'mid-game' seem to be caused by the 'location selector UI' actually.

So the demo will be messed up when using the location selector for airstrike, harrier airstrike or stealth bomber.

 

I played around with _airstrike.gsc and when you remove:

 

self beginLocationSelection( "map_artillery_selector", chooseDirection, targetSize );

 

and define chooseDirection/ targetSize in the .gsc ( so that the actual location selector map doesn't show up when using harrier airstrike etc.) it won't be messing up the demo.

Therefore it's actually the location selector UI which messes up the demos.

 

I cant find

 

self beginLocationSelection( "map_artillery_selector", chooseDirection, targetSize );

can anybody please help me?

Опубликовано:

Why do you want to change that file even?

Do you want to put it on your server?

As i already said:

"You can't fix already recorded demos by using a modified _airstrike.gsc.

The server would have needed the modified .gsc at the time you were recording.

But then you wouldn't have been able to choose the airstrike location manually. It would just have sent the airstrike to the position specified in the .gsc, without opening the location UI at all."

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Гость
Ответить в тему...

Сейчас на странице 0

  • Нет пользователей, просматривающих эту страницу

Важная информация

Используя этот сайт, вы соглашаетесь Условия использования.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.