Visible and open states of the cloud room

Options
adikus
adikus ✭✭
edited March 2013 in Native
Hi all,

Players joining room in the cloud do not see visible and open states of the current joined room. It returns false always. Only master player sees and can change it.

I'm using IOS cloud SDK.
On the version 3.0.3.x it was ok. All payers in the room could see and change visible and open states of the current room.
Starting with 3.0.4.0 only master player can do it.

Is it intended change or bug?

Thanks

Comments

  • Kaiserludi
    Kaiserludi admin
    Options
    This sounds like a bug. We will try to reproduce it.
  • Kaiserludi
    Kaiserludi admin
    Options
    Works fine for me with 3.2.0.0 with both, C++ and objC clients and the loadbalancing demo for the SDK.
    Can you provide us with an reproduction case, please?
  • adikus
    adikus ✭✭
    Options
    Steps to reproduce.
    Using objC demo provided with 3.2.0.0. Changes made in the file NetworkLogic.mm

    1) [mLoadBalancingClient connect]; //removed ip address to connect to the cloud
    2) Set Cloud AppID in initWithOutputListener
    3) Add
    [mOutputListener writeLine:@JOINED: Room isOpen: %d isVisible: %d, mLoadBalancingClient.CurrentlyJoinedRoom.IsOpen, mLoadBalancingClient.CurrentlyJoinedRoom.IsVisible];

    to the end of joinRandomRoomReturn:

    4) Running on two devices: one creates, another joins game.
    Output on the second device is:
    JOINED: Room isOpen: 0 isVisible: 0
  • Kaiserludi
    Kaiserludi admin
    Options
    Please try to set mIsOpen to true in LoadBalancingRoom::initLoadBalancingRoom() and mIsVisible to true in MutableLoadBalancingRoom::initLoadBalancingRoom() and tell me, if it then works like expected again.

    This is maybe just an initialization issue, that is leading to wrong displayed values for these 2 booleans, when no client has ever set them in that room instance and they are still on their default values.
  • Kaiserludi
    Kaiserludi admin
    Options
    Hi again.
    The fix that I have described in the previous post will also be included in the next release.

Cookies,
anyone?

We use cookies and related technologies to enhance your experience, show you personalised content and analyze performance and traffic on our website. By clicking on the „Accept All“ button you consent to the use of non-functional cookies and the subsequent processing of personal data to optimize our website and services as described in more detail in our Privacy and Cookie Policy.

By clicking on the „Customize or Deny all“ button you can decide otherwise. Clicking on the „Customize“ button will take you to a page where you can configure the usage of non-functional cookies (and related technologies) or deny all of them. You can access these settings at any time and also subsequently deselect cookies at any time in the footer area of our website.

ACCEPT ALL

Cookie Overview

We use the following categories of cookies and related technologies to enhance your experience, show you personalized content, and analyze performance and traffic on our website. We respect your right to privacy and accordingly you can chose to not allow some types of cookies (and related technologies). Click on the different category sliders and change our default settings to manage your cookie settings.

For more information on the specific cookies/related technologies we use and on how we use these, please see section 15 E. of our Privacy and Cookie Policy.

ABSOLUTELY NECESSARY

Authentication cookies we use are required to run our services … Cookies are required: Link

FUNCTIONAL AND MARKETING COOKIES

These cookies collect anonymous data and allow us to optimize our website and user experience. These cookies are listed here:

ANALYTICS

Help us to understand how visitors interact with our services, enables us to analyze and improve our services (also through third party analytics).