playMaker

Author Topic: Alternative to XML xPath / Porting to consoles  (Read 1190 times)

DennisJensen

  • Full Member
  • ***
  • Posts: 104
    • View Profile
Alternative to XML xPath / Porting to consoles
« on: August 10, 2017, 01:12:49 AM »
Hi guys

We been using dataMaker XML, and we just tried for fun if we could port our game to X Box.

We didn't think about this, but it makes sense that you can't store a XML file, it also gives a error about the xPath. It's a issue since we store progress and unlucks using XML files. Is there a alternative? In my mind we could maybe just use plain text, but would the xPath then work? Or do I have to do something differently entirely?

Also we are going to port the game to Switch, and in my mind it's going to be the same problem.
Game Designer, CEO, Artist
http://2ndStudio.com

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15205
  • Official Playmaker Support
    • View Profile
Re: Alternative to XML xPath / Porting to consoles
« Reply #1 on: August 10, 2017, 01:17:39 AM »
Hi,

 PlayerPrefs should remain accessible on console, and so your xml file because it's a string content can be saved on console for sure.

what error do you get exactly, I can have a look and provide a fix hopefully.

Xbox being run by windows, it's always really odd how they cut into .net features and shoot themselves in the foot with this, since Nintendo is different and could run without any issues at all.

 Bye,

 Jean

DennisJensen

  • Full Member
  • ***
  • Posts: 104
    • View Profile
Re: Alternative to XML xPath / Porting to consoles
« Reply #2 on: August 15, 2017, 07:38:31 AM »
Sorry about the late reply.

I been so busy. This is the error that we get.

I will test it out as with Nintendo as soon as we get the dev kit, but it sounds promising, I was worried I had to rewrite it all.
Game Designer, CEO, Artist
http://2ndStudio.com

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15205
  • Official Playmaker Support
    • View Profile
Re: Alternative to XML xPath / Porting to consoles
« Reply #3 on: August 15, 2017, 11:19:36 PM »
Hi,
 
ok, this sucks a but indeed, it seems not all Xml classes are available, and without xpath, xml is of no use really..

when publishing for console do you have access to the setting to choose the full .net 2.0 as opposed to the subset?

also have you posted on the xbox forum on wether xml is available to being with on xbox? I am trying to search but can't find anything on this... maybe when you have access to xbox publishing you can ask within the dev group?

Bye,

 Jean



Bye,

 Jean

DennisJensen

  • Full Member
  • ***
  • Posts: 104
    • View Profile
Re: Alternative to XML xPath / Porting to consoles
« Reply #4 on: August 25, 2017, 01:17:25 AM »
Sorry about the slow response, we are going to showcase our game at PAX so there is a lot at the moment.

We tried to choose full .net 2.0 but with no result, we still get the same error.

I will see if I can get a answer from MS, I just wrote them a email.

Cheers
Game Designer, CEO, Artist
http://2ndStudio.com

jeanfabre

  • Administrator
  • Hero Member
  • *****
  • Posts: 15205
  • Official Playmaker Support
    • View Profile
Re: Alternative to XML xPath / Porting to consoles
« Reply #5 on: August 25, 2017, 01:44:52 AM »
Hi,

 crap...

I have seen here and there that some crazy devs are able to just bring in more from the .net library manually, maybe looking and searching within the .net devs messing with Unity could lead you to be able to bring in the missing xml libs insied Unity when publishing.
 
It's such a pain, how come xml doesn't make it on console, that's beyond me... such a basic and powerful way to deal with data. I am really sorry I can't be of more help on this...

 Bye,

 Jean

DennisJensen

  • Full Member
  • ***
  • Posts: 104
    • View Profile
Re: Alternative to XML xPath / Porting to consoles
« Reply #6 on: September 27, 2017, 08:09:40 AM »
@jean

No worries we will figure it out :)
Game Designer, CEO, Artist
http://2ndStudio.com